On May 10, 2010, at 11:36 AM, William A. Rowe Jr. wrote: > On 5/10/2010 1:28 PM, Daniel Ruggeri wrote: >> Hi, all. >> I found this document today stating the following: >> Each developer is responsible for notifying the mailing list and >> adding an action item to STATUS when they have an idea for a new feature >> or major change to propose for the product. >> Since I am not a committer, how would I go about having my submitted >> patch added to the STATUS file in the 2.2 branch after it has been >> "FixedInTrunk"?
Speaking for myself only, we seem to have an interesting symbiosis with Bugzilla. We all agree it's necessary to have a formal issue tracker, but the informal discussion on dev@ often works faster and smoother. > Just post a patch to the dev@ list. The plain text would be fine by me, > but you want to ensure any committer can patch STATUS for you, no matter > which workflow they use. I agree with wrowe. Check out http://svn.apache.org/repos/asf/httpd/httpd/branches/2.2.x and edit STATUS. See the existing backport proposals for guidance on formatting. Then run svn diff STATUS and send the result to the list. If the backported patch materially differs from the revision changes in trunk, I'd suggest either publishing a patch against 2.2.x HEAD somewhere (anywhere) or attaching it to your patch for STATUS. S. -- Sander Temme scte...@apache.org PGP FP: 51B4 8727 466A 0BC3 69F4 B7B8 B2BE BC40 1529 24AF
