On 6 Feb 2011, at 16:04, 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).
+1
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; [...]
Mmmm, yes, shiny... I like the graphs. What were we discussing again?
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 would suggest that, of the many things that a Subversion commit
hook *could* do, this ought to rank way ahead of checking for
whitespace at the end of lines as something that will increase
project quality. And, of course, for those of us using QIPs for new
feature tracking, simply create a JIRA with the QIP text as
description (Some people, I noticed, have been doing this already)
and track commits and status via JIRA.
And, as I suggested in a previous message, we can create 'catch-all'
JIRAs for commits that small or generic, specific to each release/
version. The release manager would be responsible for creating these,
for example: 'Java broker changes', 'C++ client changes' and so
forth, marked as 'fixed in' whatever particular version.
[...] I think it should be so infrequent that enforcing 100%
inclusion of
JIRA commit references really is the way to go here, as the above
results
are somewhat ridiculous.
See above.
Andrew.
--
-- andrew d kennedy ? do not fold, bend, spindle, or mutilate ;
-- http://grkvlt.blogspot.com/ ? edinburgh : +44 7582 293 255 ;
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org
