Re: FixedInTrunk keyword?
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
Re: FixedInTrunk keyword?
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? Thanks -Daniel Ruggeri Daniel Ruggeri wrote: Sander/All; Oh, I see. I guess my next question is how the issue fixed in trunk gets proposed in the STATUS list. I submitted a patch that was added to trunk, but am unsure if there is any additional action to take on my part. P.S. Also, is this information or process noted anywhere? I apologize for polluting the general mailing list with basic process questions. -- Daniel Ruggeri Sander Temme wrote: On Apr 20, 2010, at 12:41 PM, Daniel Ruggeri wrote: Hi all; I have a little confusion regarding the FixedInTrunk keyword when applied to a bug. What does it mean? My assumption is that it means that the code changes needed to fix the bug have been committed to the source repository and the fix will be available in the next stable release. Once that happens, the bug will be closed. Is this accurate? That's not how I read it. The current stable releases are taken from the 2.2.x branch. Issues fixed in trunk are proposed for backport in the STATUS file: http://svn.apache.org/viewvc/httpd/httpd/branches/2.2.x/STATUS and backported once they collect the requisite three +1 votes. A FixedInTrunk keyword would allow you to take the fix and backport it on your own, ahead of any activity by the httpd project, should you have a need to do so. S. Thank you for your time answering my simple question -Daniel Ruggeri
Re: FixedInTrunk keyword?
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? 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.
Re: Re: FixedInTrunk keyword?
Sander/All; Oh, I see. I guess my next question is how the issue fixed in trunk gets proposed in the STATUS list. I submitted a patch that was added to trunk, but am unsure if there is any additional action to take on my part. P.S. Also, is this information or process noted anywhere? I apologize for polluting the general mailing list with basic process questions. -- Daniel Ruggeri Sander Temme wrote: On Apr 20, 2010, at 12:41 PM, Daniel Ruggeri wrote: Hi all; I have a little confusion regarding the FixedInTrunk keyword when applied to a bug. What does it mean? My assumption is that it means that the code changes needed to fix the bug have been committed to the source repository and the fix will be available in the next stable release. Once that happens, the bug will be closed. Is this accurate? That's not how I read it. The current stable releases are taken from the 2.2.x branch. Issues fixed in trunk are proposed for backport in the STATUS file: http://svn.apache.org/viewvc/httpd/httpd/branches/2.2.x/STATUS and backported once they collect the requisite three +1 votes. A FixedInTrunk keyword would allow you to take the fix and backport it on your own, ahead of any activity by the httpd project, should you have a need to do so. S. Thank you for your time answering my simple question -Daniel Ruggeri
FixedInTrunk keyword?
Hi all; I have a little confusion regarding the FixedInTrunk keyword when applied to a bug. What does it mean? My assumption is that it means that the code changes needed to fix the bug have been committed to the source repository and the fix will be available in the next stable release. Once that happens, the bug will be closed. Is this accurate? Thank you for your time answering my simple question -Daniel Ruggeri
Re: FixedInTrunk keyword?
On Apr 20, 2010, at 12:41 PM, Daniel Ruggeri wrote: Hi all; I have a little confusion regarding the FixedInTrunk keyword when applied to a bug. What does it mean? My assumption is that it means that the code changes needed to fix the bug have been committed to the source repository and the fix will be available in the next stable release. Once that happens, the bug will be closed. Is this accurate? That's not how I read it. The current stable releases are taken from the 2.2.x branch. Issues fixed in trunk are proposed for backport in the STATUS file: http://svn.apache.org/viewvc/httpd/httpd/branches/2.2.x/STATUS and backported once they collect the requisite three +1 votes. A FixedInTrunk keyword would allow you to take the fix and backport it on your own, ahead of any activity by the httpd project, should you have a need to do so. S. Thank you for your time answering my simple question -Daniel Ruggeri -- Sander Temme scte...@apache.org PGP FP: 51B4 8727 466A 0BC3 69F4 B7B8 B2BE BC40 1529 24AF
