Stas Bekman wrote:
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.
Which will prevent from most people to see the discussions at a timely manner. You should really look at RT which gives you the best of the both worlds.
In any case, my suggestion was to make easier for users generate the correct subjects and not to automatically generate an email here, but just a link.
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.
For the same reason we ask people to inline the patches when posting to the list, and not attach them (easier to comment on in reply and doesn't require special steps in order to view the patch), I think that on the opposite the patch should be inlined and a pointer to the original patch posted along, in case the patch included tabs or some other chars that may not survive inlining.
[...] __________________________________________________________________ Stas Bekman JAm_pH ------> Just Another mod_perl Hacker http://stason.org/ mod_perl Guide ---> http://perl.apache.org mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com http://modperlbook.org http://apache.org http://ticketmaster.com
