On 02/06/2011 11:04 AM, Robbie Gemmell wrote:
As I recently indicated on the QIP discussion thread, I think we need to
make better use of JIRA to benefit both our users and ourselves. Too many of
our commits have no JIRA listed, and in many cases this is not just failure
to include the reference but a failure to even create a JIRA at all. In the
former case, this means people can't link a JIRA to its changes and often
makes it impossible for the Release Manager to tidy up (not that they should
have to, really...) JIRAs that have not been updated properly, and in the
latter case it means people have no way of determining a change was even
made without viewing the commit logs for themselves (and having some idea
what the change actually means).
The shiny new JIRA version now in use at the ASF has a nice page for viewing
commits to a project and what JIRA they reference etc, including only those
for a particular release version. It would be more useful if it was actually
able to include most of our commits; currently it isn't able to because it
needs a JIRA reference in the commit log (at the time of the commit) in
order to work. You can see it in [in]action at:
https://issues.apache.org/jira/browse/QPID#selectedTab=com.atlassian.jira.pl
ugin.ext.subversion%3Asubversion-project-tab
I suggested that we are so bad at this that we need a commit hook to enforce
inclusion of JIRA tags in our commit logs. Gordon thought that perhaps a
name-and-shame approach would work better to enforce the spirit rather than
the letter of the law. I present our last 3 months of commits in a table,
coloured green or red depending on whether they included a JIRA reference or
not: https://cwiki.apache.org/confluence/display/qpid/Commit+List
I bow my head in shame. I've been a repeat offender on this, I will clean up my
act.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org
