You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@stdcxx.apache.org by fa...@apache.org on 2012/01/12 00:59:35 UTC
svn commit: r1230331 - in /stdcxx/site: bugs.html
forrest/src/documentation/content/xdocs/bugs.xml
Author: faridz
Date: Wed Jan 11 23:59:34 2012
New Revision: 1230331
URL: http://svn.apache.org/viewvc?rev=1230331&view=rev
Log:
2012-01-12 Farid Zaripov <fa...@apache.org>
* bugs.html: Update mailing list emails.
* forrest/src/documentation/content/xdocs/bugs.xml: Same.
Modified:
stdcxx/site/bugs.html
stdcxx/site/forrest/src/documentation/content/xdocs/bugs.xml
Modified: stdcxx/site/bugs.html
URL: http://svn.apache.org/viewvc/stdcxx/site/bugs.html?rev=1230331&r1=1230330&r2=1230331&view=diff
==============================================================================
--- stdcxx/site/bugs.html (original)
+++ stdcxx/site/bugs.html Wed Jan 11 23:59:34 2012
@@ -186,7 +186,7 @@ href="index.html#references">reference</
confirm that the behavior you are experiencing is, in fact, a bug and
not a feature. If even after reading the relevant references you are
still not sure, you should send an email to <a
-href="mailto:stdcxx-user@incubator.apache.org">stdcxx-user@incubator.apache.org</a>
+href="mailto:user@stdcxx.apache.org">user@stdcxx.apache.org</a>
and ask. If the problem is indeed a bug, go back to step 1.
</p>
@@ -590,7 +590,7 @@ someone else reported, you can do so in
<li>
Post the patch to the project development mailing list, <a
-href="mailto:stdcxx-dev@incubator.apache.org">stdcxx-dev@incubator.apache.org</a>. The
+href="mailto:dev@stdcxx.apache.org">dev@stdcxx.apache.org</a>. The
subject line of the email should start with the string [PATCH],
followed by a brief description of the patch and the issue number from
the issue tracking database if one exists. An easy way to come up
@@ -630,7 +630,7 @@ in the issue tracking database and at
small changes, post the patch along with a detailed description as
well as before and after data showing the improvement to the project
development mailing list, <a
-href="mailto:stdcxx-dev@incubator.apache.org">stdcxx-dev@incubator.apache.org</a>.
+href="mailto:dev@stdcxx.apache.org">dev@stdcxx.apache.org</a>.
</p>
<p>
Modified: stdcxx/site/forrest/src/documentation/content/xdocs/bugs.xml
URL: http://svn.apache.org/viewvc/stdcxx/site/forrest/src/documentation/content/xdocs/bugs.xml?rev=1230331&r1=1230330&r2=1230331&view=diff
==============================================================================
--- stdcxx/site/forrest/src/documentation/content/xdocs/bugs.xml (original)
+++ stdcxx/site/forrest/src/documentation/content/xdocs/bugs.xml Wed Jan 11 23:59:34 2012
@@ -34,7 +34,7 @@ A computer bug is an error, flaw, mistak
<title>Before Reporting a Bug</title>
<ol>
<li>If you have discovered a bug in stdcxx and would like to report it to the development team, please be sure to first check the project's issue tracking database to see whether the bug has already been reported and, if so, what its status is. If the bug has not been reported yet, follow the instructions on Reporting a Bug below. Otherwise, feel free to add a comment to the issue in the issue tracking database if you think it might help resolve it more quickly (for example, if you have a smaller or better test case).</li>
- <li>If you think but aren't 100% sure that you have discovered a bug in the source code of the project, please consult a reliable reference on the subject first and confirm that the behavior you are experiencing is, in fact, a bug and not a feature. If even after reading the relevant references you are still not sure, you should send an email to stdcxx-user@incubator.apache.org and ask. If the problem is indeed a bug, go back to step 1.</li>
+ <li>If you think but aren't 100% sure that you have discovered a bug in the source code of the project, please consult a reliable reference on the subject first and confirm that the behavior you are experiencing is, in fact, a bug and not a feature. If even after reading the relevant references you are still not sure, you should send an email to user@stdcxx.apache.org and ask. If the problem is indeed a bug, go back to step 1.</li>
<li>If you have a suggestion for a change or an addition to the interface or the behavior of this implementation of the library that you would like to propose to the development team (e.g., an enhancement request), please make sure that the change is not in conflict with the requirements of the C++ Standard. You can get an electronic copy of the C++ Standard from the ANSI eStandards store. If your request is not in conflict with any requirements of the C++ standard, open a request for Improvement or New Feature to the issue tracking database (see the stdcxx issue tracking database documentation for the available issue types).</li>
</ol>
</section>
@@ -65,11 +65,11 @@ A computer bug is an error, flaw, mistak
<title>Submitting Patches</title>
<p>Committers who follow the Review-Then-Commit policy, and non-committer Contributors without commit (write) access to the stdcxx source repository must submit patches for review and approval before they can be committed by someone with commit access. If you would like to submit a patch for a bug that you or someone else reported, you can do so in two ways:</p>
<ol>
- <li>Post the patch to the project development mailing list, stdcxx-dev@incubator.apache.org. The subject line of the email should start with the string [PATCH], followed by a brief description of the patch and the issue number from the issue tracking database if one exists. An easy way to come up with a good description for the patch subject line is to simply copy the Summary from the bug report. Be sure to also include a reference to the bug (preferably in the form of a link to the original bug report).</li>
+ <li>Post the patch to the project development mailing list, dev@stdcxx.apache.org. The subject line of the email should start with the string [PATCH], followed by a brief description of the patch and the issue number from the issue tracking database if one exists. An easy way to come up with a good description for the patch subject line is to simply copy the Summary from the bug report. Be sure to also include a reference to the bug (preferably in the form of a link to the original bug report).</li>
<li>Add the patch to the bug report in the form of a comment (when the patch is just a few lines of text), or in the form of an attachment to the issue. This approach is preferable to sending the patch to the mailing list when the patch is large or when the patch sent to the project development mailing list gets mangled or stripped by the list management software.</li>
</ol>
<p>If you would like to submit a patch for a bug that doesn't have a corresponding issue in the issue tracking database, you should start by creating a small test case to demonstrate the problem first. It's not uncommon for this exercise to expose an error in the usage of the library rather than in the library implementation itself. Once you've isolated the bug to a small test case and filed an issue in the issue tracking database you can update the issue with the proposed patch.</p>
- <p>If you would like to submit a patch with an improvement to the project (such as an optimization tweak), either create an enhancement request in the issue tracking database and attach the patch to it or, for small changes, post the patch along with a detailed description as well as before and after data showing the improvement to the project development mailing list, stdcxx-dev@incubator.apache.org.</p>
+ <p>If you would like to submit a patch with an improvement to the project (such as an optimization tweak), either create an enhancement request in the issue tracking database and attach the patch to it or, for small changes, post the patch along with a detailed description as well as before and after data showing the improvement to the project development mailing list, dev@stdcxx.apache.org.</p>
<p>Patches for documentation or project web pages should follow the same process as above, except that a test case isn't necessary in most situations. A possible exception is a patch for code example listed in the Class Reference.</p>
<p>In all cases, make sure your patch follows the expected Patch Format described below.</p>
</section>