Jeff Trawick wrote:
- make sure that the PR # is in the subject of any on-list discussion of the patch
Why not automate this process. Change bugzilla to do the job and autogenerate the right link:
<a hred="mailto:[EMAIL PROTECTED]">Post the patch to the httpd-dev list]</a>
In that bullet ("make sure that the PR #") I just wanted to point out that IFF the submitter has something technical to discuss on dev@ or wants to try to get support for the concept on dev@, at least make sure the subject line mentions the bugzilla entry. While it is more natural to have a discussion on dev@ than via bugzilla, I think we should optimize for the people willing to go query bugzilla and see what patches are unresolved. Right now, that means keep as much discussion as possible in bugzilla.
It would be great to autogenerate a dev@ post when the PatchAvailable keyword is added in order to give awareness to everybody. The subject would be "[PATCH PR #12345] <bugzilla summary>" and the body would be the URL of the entry. And if the submitter wishes to discuss on the list, they can respond to that post. I just don't think we have to post the patch itself, or imply with the button that the patch needs to be submitted in two places.
<warning>
I'm not about to mess with Bugzilla or RT or anything else. Whoever is willing can pretty much make it work the way they want to and I will go along, in exchange for having more time to work directly on Apache. Heck, even Gnats didn't upset me. The process is not set in stone and is expected to be continually improved. I just didn't want to wait for something more perfect.
</warning>
The cool thing about RT is that it does all this for you and all discussions at the list are "blogged" into the bug record.
That sounds like a huge improvement.
