> Might want to make the ticket expression /ZF\-\d+/ just to make maintenance of > the hook easier. You'll also want to prevent commits to tickets that are > closed.
That would require a JIRA lookup, which means Jira would have to be running 100% of the time and without load. Not sure that requirement can be met at this time but we are getting there. > The way that I've worked in the past with hooks like these is to use open > tickets for common tasks so that all Spanish documentation updates are > ZF-12345, for example, and this ticket tracks all Spanish language changes. > Everything else (including general maintenance) is then tracked through a > ticket. It can be a ticket like "Reorganization of repository layout" or > whatever, but it helps keep everything in one place and makes it easily > searchable. I don't know - Wil prob has more of an opinion on the matter (about standing open bugs). Lemme ping him. > For projects with a large number of committers, I've found this to be the best > way to keep things organized. That's what is prompting all of this :) -- Ralph Schindler Software Engineer | [EMAIL PROTECTED] Zend Framework | http://framework.zend.com/
