Either a ticket or just sent to the mail list for Commons in general. The difference being:
patch attached to bugzilla means it willg et in eventually [by next release] patch attached to email means it's highly likely it'll go into the CVS HEAD, but when few people are paying enough attention, those kinds of patches can leak through. My view is that if it doesn't feel as though anyone is chomping at the bit to patch the code, attach it to bugzilla and send an email mentioning this was done. Hen On Mon, 3 Mar 2003, David Graham wrote: > I'm not sure how commons works but patches are normally attached to a > bugzilla ticket for Struts. > > David > > > > >From: "Quinton McCombs" <[EMAIL PROTECTED]> > >Reply-To: "Jakarta Commons Developers List" > ><[EMAIL PROTECTED]> > >To: "Jakarta Commons Developers List" <[EMAIL PROTECTED]> > >Subject: RE: [POOL] Pool listeners > >Date: Mon, 3 Mar 2003 14:01:22 -0600 > > > >I have completed the implementation of pool listeners. How should I > >submit the patches? > > > >--------------------------------------------------------------------- > >To unsubscribe, e-mail: [EMAIL PROTECTED] > >For additional commands, e-mail: [EMAIL PROTECTED] > > > _________________________________________________________________ > Protect your PC - get McAfee.com VirusScan Online > http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963 > > > --------------------------------------------------------------------- > 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]
