Author: sebor
Date: Thu Jul 26 17:55:44 2007
New Revision: 560044
URL: http://svn.apache.org/viewvc?view=rev&rev=560044
Log:
2007-07-26 Martin Sebor <[EMAIL PROTECTED]>
* index.html: Added a blurb about contributors having read
and not write access to the source code repository.
* bugs.html: Expanded the section on Submitting Patches.
Modified:
incubator/stdcxx/site/bugs.html
incubator/stdcxx/site/index.html
Modified: incubator/stdcxx/site/bugs.html
URL:
http://svn.apache.org/viewvc/incubator/stdcxx/site/bugs.html?view=diff&rev=560044&r1=560043&r2=560044
==============================================================================
--- incubator/stdcxx/site/bugs.html (original)
+++ incubator/stdcxx/site/bugs.html Thu Jul 26 17:55:44 2007
@@ -379,8 +379,14 @@
<div class="section">
<p>
-If you would like to submit a patch for a bug that you or someone else
-reported, you can do so in two ways:
+<a href="index.html#committers">Committers</a> who follow the <a
+href="http://www.apache.org/foundation/glossary.html#ReviewThenCommit";>Review-Then-Commit</a>
+policy, and non-committer <a
+href="index.html#contributors">Contributors</a> 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>
@@ -389,18 +395,21 @@
Post the patch to the project development mailing list, <a
href="mailto:[EMAIL PROTECTED]">[EMAIL PROTECTED]</a>. The
subject line of the email should start with the string [PATCH],
-followed by a brief description of the patch. 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).
+followed by a brief description of the patch and the issue number from
+the bug 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.
+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>
@@ -422,6 +431,14 @@
description as well as before and after data showing the improvement
to the project development mailing list, <a
href="mailto:[EMAIL PROTECTED]">[EMAIL PROTECTED]</a>.
+
+ </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>
Modified: incubator/stdcxx/site/index.html
URL:
http://svn.apache.org/viewvc/incubator/stdcxx/site/index.html?view=diff&rev=560044&r1=560043&r2=560044
==============================================================================
--- incubator/stdcxx/site/index.html (original)
+++ incubator/stdcxx/site/index.html Thu Jul 26 17:55:44 2007
@@ -795,6 +795,15 @@
</p>
<p>
+Because Contributors have read but not write access to stdcxx code
+repository, they can check stdcxx out and make changes to their local
+copy of stdcxx files but they cannot check them back in. To get their
+changes committed, they must follow the process for <a
+href="bugs.html#patches">Submitting Patches</a>.
+
+ </p>
+ <p>
+
The stdcxx community welcomes new contributors. If you are interested
in getting involved, the first thing to do after reading the project
Web pages is to subscribe to the <a
