I've recently been reviewing the outstanding issues in preparation for the 1.5 release. I have noticed that issues including patches have in some cases remained in limbo for months in the issue tracker, so it is my intention to work with the component leads to first get through this backlog of patches *before* 1.5 and then to provide some guidelines for how long an issue with a patch can be left unresolved without either thumbs up and a corresponding checkin or a thumbs down and an explanation. In my mind, anyone who has gone through the trouble of writing and submitting a patch deserves an up or down vote within a week or so. I will be exploring possibilities for changes in our process to make sure these patches don't slip through the cracks. My first take on it is to document the process of submitting a patch in the contributors' guide, adding instructions that everyone use the 'patch' issue type so that we can properly report against them and a clarification that it is the *submitter's* responsibility to make sure they get on to trunk in a tested state after they have been approved by the component lead to the information already contained in this doc: http://framework.zend.com/wiki/display/ZFUSER/Submitting+a+Bug+Fix. As always, I'm open to any suggestions here.
Thanks. ,Wil > -----Original Message----- > From: Trevor Johns [mailto:[EMAIL PROTECTED] > Sent: Saturday, December 15, 2007 3:32 PM > To: Jordan Moore > Cc: [email protected] > Subject: Re: [fw-general] Patches > > On Dec 13, 2007, at 1:38 PM, Jordan Moore wrote: > > > I've recently been added to the developer's group in JIRA. I've been > > going through the issue tracker and submitting patches for a number > of > > small bugs. Do I just wait for someone with SVN access to test and > > commit them, or is there some other step I'm supposed to take? > > > Submitting them to JIRA should be enough, assuming that somebody with > commit access is keeping an eye on the bug (component coordinators > automatically get emailed about everything in their component, so this > should always be the case). > > However, if they sit around for too long, feel free to ping the > respective mailing list. :) > > -- > Trevor Johns > http://tjohns.net
