+1. I like having one place, Bugzilla, as the 'repository' for patches as opposed to email lists.
Gary > -----Original Message----- > From: sebb [mailto:[EMAIL PROTECTED] > Sent: Sunday, March 26, 2006 3:42 AM > To: Jakarta General List > Subject: Submitting patches > > Generally I find that patches are much easier to process as Bugzilla > attachments, rather than sent to the developer list as an attachment. > > And if the patch is large, it uses everyones mail resources, most of > whom aren't interested. > > Just received such a patch on JMeter - the poster helpfully has a blog > where he says that he followed the guidelines in: > > http://jakarta.apache.org/site/source.html#Patches > > which do indeed suggest sending patches to the developer mailing list. > > I'd like to suggest a change, so that the preferred method of > submitting patches is via Bugzilla or JIRA. > > In the case of projects using JIRA, I believe that asks for a software > grant, so it's important that code is submitted that way. > > [Actually, I'm not sure when emailed patches are appropriate...] > > I'd also like to split the patch section into two: > > Patch Creation > > Patch Submission > > Any objections to this? > > If not, I'll make a start on updating the text - and put a copy on my > home page for review. > > Sebastian (sebb AT AO) > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
