Some SCMs can be configured to only allow commits using an assiciated ticket... e.g. there are commit hocks which would check for ticket existence... maybe there exists a pre commit hock for SVN that would parse the commit comment for the availability of a JIRA ID...
Cheers Daniel On Fri, Jan 20, 2012 at 7:29 PM, Romain Manni-Bucau <[email protected]> wrote: > We cant disagree but it stays words... > > Maybe another tool to add to release tools can help or a buildbot hook: if > no jira id send a mail. > > - Romain > > Le 20 janv. 2012 19:24, "David Blevins" <[email protected]> a écrit : > >> Big features don't come in one commit. That's the thing to remember. >> I'll come back to that thought shortly.... >> >> Here are some stats from beta-1 to beta-2: >> >> - There were 436 commits total. (whoo hoo!!) >> - Only 69 of those commits had JIRAs (eek!) >> >> So first, totally awesome to see all the activity. Second, lets find some >> way to improve our JIRA usage. >> >> Back to the original thought; big features don't come in one commit. >> >> Over the course of years I've noticed that most the new feature JIRAs are >> filed at the end of the release. I've also noticed that most of the >> changes without JIRA numbers go to these new features or enhancements. >> >> That makes sense as big changes don't come in one commit. But that >> doesn't mean there shouldn't be a JIRA issue. We could file a JIRA for the >> overall change and just keep reusing it on each of the many tiny commits >> that relate. >> >> Seems like a good middle ground. Having to create a new JIRA for every >> commit is annoying and noisy, having no JIRAs makes for some empty release >> notes (or an incredible amount of time spent picking through commits >> looking for potential JIRAs). >> >> >> Thoughts? >> >> >> -David >> >>
