boost/more
1
0
Fork 0
mirror of https://github.com/boostorg/more.git synced 2025-01-14 02:20:08 +08:00
Code Issues Packages Projects Releases Wiki Activity

Add Bugs and New Features pages, plus links to them in other pages

Browse Source 
[SVN r12347]
This commit is contained in:
Beman Dawes 2002-01-18 16:38:31 +00:00
parent 1842034c4c
commit 7dc0a4321c
4 changed files with 142 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

80
bugs.htm Normal file
View File

@ -0,0 +1,80 @@
<html>
<head>
<meta http-equiv="Content-Language" content="en-us">
<meta http-equiv="Content-Type" content="text/html; charset=windows-1252">
<meta name="GENERATOR" content="Microsoft FrontPage 5.0">
<meta name="ProgId" content="FrontPage.Editor.Document">
<title>Bugs</title>
</head>
<body bgcolor="#FFFFFF" text="#000000">
<table border="1" bgcolor="#007F7F" cellpadding="2">
<tr>
<td bgcolor="#FFFFFF">
<img src="../c++boost.gif" alt="c++boost.gif (8819 bytes)" width="277" height="86"></td>
<td><a href="../index.htm"><font face="Arial" color="#FFFFFF"><big>Home</big></font></a></td>
<td><a href="../libs/libraries.htm"><font face="Arial" color="#FFFFFF"><big>
Libraries</big></font></a></td>
<td><a href="../people/people.htm"><font face="Arial" color="#FFFFFF"><big>
People</big></font></a></td>
<td><a href="faq.htm"><font face="Arial" color="#FFFFFF"><big>FAQ</big></font></a></td>
<td><a href="index.htm"><font face="Arial" color="#FFFFFF"><big>More</big></font></a></td>
</tr>
</table>
<h1>What to do about Boost bugs</h1>
<ol>
<li>Make sure the bug isn't already fixed in the latest sources. The most
recent version of everything on the Boost web site is available from
<a href="http://www.boost.org/more/download.html#CVS">boost public CVS
repository</a>.<br>
&nbsp;</li>
<li>If you are a Boost user, or a Boost developer that doesn't have a CVS
write access: <br>
&nbsp;<ol>
<li>Submit a bug report to either
<a href="http://www.boost.org/more/mailing_lists.htm#users">boost-users list</a>,
<a href="http://www.boost.org/more/mailing_lists.htm#main">boost mailing
list</a>, or our <a href="http://sourceforge.net/tracker/?group_id=7586">bug
tracking facility</a> at SourceForge; submitting it to either of the mailing
lists is a preferred way - because many of the Boost developers read the
lists on a daily basis, this way you are likely to get a quicker response,
and the discussions that often arise there from (possible) bug reports are
quite interesting and educational as well;<br>
&nbsp;</li>
<li>If you have a proposed patch to the code, post it along with your bug
report, preferably in the <em>context diffs</em> format (<code>diff -c</code>);
if you can, send a patch relative to the current CVS state. <br>
&nbsp;</li>
</ol>
</li>
<li>If you are a Boost developer, and you have a CVS write access: <br>
&nbsp;<ol>
<li>If bug is trivial (e.g. misspelled name, missed <code>typename</code>,
etc.), and you are willing to make a fix, either make your changes locally
and contact the library author(s)/maintainer(s) about it, or go ahead and
check the fix into CVS, but post a notification about it to the
<a href="http://www.boost.org/more/mailing_lists.htm#main">boost mailing
list</a> (if the author is not very active on the list, you also might want
to consider <code>cc</code>'ing him as well); <br>
&nbsp;</li>
<li>If bug is non-trivial, or/and you don't have time/resources to fix it,
submit a bug report (see p. 2 above); chances are that the maintainer(s)
will respond promptly and take care of the problem; <br>
&nbsp;</li>
<li>Otherwise create a temporary branch in CVS, make your changes there, and
ask the library author(s)/maintainer(s) to review them; if they are ok with
the new code, either you or they can integrate the fixes into the main
trunk. </li>
</ol>
</li>
</ol>
<hr>
<p>Contributed by <a href="../people/aleksey_gurtovoy.htm">Aleksey Gurtovoy</a></p>
<p>Revised <!--webbot bot="Timestamp" s-type="EDITED" s-format="%d %B, %Y" startspan -->18 January, 2002<!--webbot bot="Timestamp" i-checksum="38453" endspan -->
</p>
</body>
</html>

8
faq.htm
View File

@ -159,9 +159,15 @@ extension communicates nothing and forces inspection of file contents to
determine type. Using '.hpp' unambiguously identifies it as C++ header file, and determine type. Using '.hpp' unambiguously identifies it as C++ header file, and
works well in actual practice. (Rainer Deyke)</p> works well in actual practice. (Rainer Deyke)</p>
<p><b>What should I do if I spot a bug in the Boost code or documentation?</b>
See the suggestions on the <a href="bugs.htm">Bugs page</a>.</p>
<p><b>How can I request a new feature in a Boost Library? </b>See the
<a href="requesting_new_features.htm">Requesting New Features</a> page.</p>
<hr> <hr>
<p>Revised <!--webbot bot="Timestamp" S-Type="EDITED" S-Format="%d %B, %Y" startspan -->26 December, 2001<!--webbot bot="Timestamp" i-checksum="38515" endspan --> <p>Revised <!--webbot bot="Timestamp" S-Type="EDITED" S-Format="%d %B, %Y" startspan -->18 January, 2002<!--webbot bot="Timestamp" i-checksum="38453" endspan -->
</p> </p>
</body> </body>
</html> </html>

6
index.htm
View File

@ -73,6 +73,10 @@ content="text/html; charset=iso-8859-1">
Describes what other headers each boost header includes.</p> Describes what other headers each boost header includes.</p>
<p><b><a href="proposal.pdf">Proposal for a C++ Library Repository Web Site</a></b>&nbsp; <p><b><a href="proposal.pdf">Proposal for a C++ Library Repository Web Site</a></b>&nbsp;
The original 1998 proposal that launched Boost.</p> The original 1998 proposal that launched Boost.</p>
<p><b><a href="bugs.htm">How to report bugs</a></b>&nbsp; Ways to report
Boost bugs.</p>
<p><b><a href="requesting_new_features.htm">How to request features</a></b>
Ways to request new library features.</p>
</blockquote> </blockquote>
<h2>Articles and Papers</h2> <h2>Articles and Papers</h2>
@ -126,6 +130,6 @@ content="text/html; charset=iso-8859-1">
<hr> <hr>
<p>Revised <!--webbot bot="Timestamp" s-type="EDITED" <p>Revised <!--webbot bot="Timestamp" s-type="EDITED"
s-format="%d %B, %Y" startspan -->20 November, 2001<!--webbot bot="Timestamp" i-checksum="39351" endspan --></p> s-format="%d %B, %Y" startspan -->18 January, 2002<!--webbot bot="Timestamp" i-checksum="38453" endspan --></p>
</body> </body>
</html> </html>

50
requesting_new_features.htm Normal file
View File

@ -0,0 +1,50 @@
<html>
<head>
<meta http-equiv="Content-Language" content="en-us">
<meta http-equiv="Content-Type" content="text/html; charset=windows-1252">
<meta name="GENERATOR" content="Microsoft FrontPage 5.0">
<meta name="ProgId" content="FrontPage.Editor.Document">
<title>Requesting New Features</title>
</head>
<body bgcolor="#FFFFFF" text="#000000">
<table border="1" bgcolor="#007F7F" cellpadding="2">
<tr>
<td bgcolor="#FFFFFF">
<img src="../c++boost.gif" alt="c++boost.gif (8819 bytes)" width="277" height="86"></td>
<td><a href="../index.htm"><font face="Arial" color="#FFFFFF"><big>Home</big></font></a></td>
<td><a href="../libs/libraries.htm"><font face="Arial" color="#FFFFFF"><big>
Libraries</big></font></a></td>
<td><a href="../people/people.htm"><font face="Arial" color="#FFFFFF"><big>
People</big></font></a></td>
<td><a href="faq.htm"><font face="Arial" color="#FFFFFF"><big>FAQ</big></font></a></td>
<td><a href="index.htm"><font face="Arial" color="#FFFFFF"><big>More</big></font></a></td>
</tr>
</table>
<h1>Requesting new features for Boost libraries</h1>
<p>If you have an idea for a feature or improvement to an existing Boost library
- go ahead and post it to either
<a href="http://www.boost.org/more/mailing_lists.htm#users">boost-users list</a>
or <a href="http://www.boost.org/more/mailing_lists.htm#main">boost mailing list</a>
(if you are posting for the first time, please read our
<a href="http://www.boost.org/more/discussion_policy.htm">discussion policy</a>
before you actually post). </p>
<p>You can also use our <a href="http://sourceforge.net/tracker/?group_id=7586">
feature request tracking facility</a> at SourceForge, but experience has shown
that posting to either of the mailing lists is usually a more effective way to
get attention of boost developers. </p>
<p>If your proposal has its merits, it's very likely that it will generate a
constructive discussion that might actually result in (sometimes substantial)
improvement of the library - and your name being put on the library's
<a href="http://www.boost.org/more/lib_guide.htm#Acknowledgements">
Acknowledgements</a> section! </p>
<hr>
<p>Contributed by <a href="../people/aleksey_gurtovoy.htm">Aleksey Gurtovoy</a></p>
<p>Revised <!--webbot bot="Timestamp" s-type="EDITED" s-format="%d %B, %Y" startspan -->18 January, 2002<!--webbot bot="Timestamp" i-checksum="38453" endspan -->
</p>
</body>
</html>