On Tue, 2011-02-08 at 13:14 +0000, Robbie Gemmell wrote: > I largely agree with Rajith as shown by my commit history, there are > some changes I dont think warrant a JIRA such as random litle README > or website changes (however, larger documentation changes should > generally be associated with a JIRA because surely they are > documenting something that was implemented or fixed). > > The problem defining where that line is and then not crossing it; > results suggest we have proven absolutely incapable of doing that as a > group so far. Also, as mentioned there are tools such as the JIRA > commit list that require a JIRA tag in order to work at all; it would > be good for everything to be visible there.
Perhaps we could resolve this by creating catchall JIRAs for the various categories of trivial checkins. Say: One for License additions, one for typos in comments, one for trivial documentation changes there are probably categories to add here. Lets not spend too long on this though. I'm unclear whether there are any code changes sufficiently trivial for a catchall, but there may be. I prefer having a rough categorisation as this will stop people from just adding QPID-xxxx to every simple checkin and require a small amount of thought for every checkin. Once we have these catch-alls then we could have a check in hook that requires a valid QPID-???? bug number in the checkin comment, without affecting trivial checkins. Andrew --------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
