On 10/14/06, Martin Marinschek <[EMAIL PROTECTED]> wrote:
+1 for applying this rule to all non-trivial commits.
A habit that Struts and Shale (among others) have adopted in this regard is to have "omnibus" issues open for capturing the large number of small-scale commits that contribute to some overall goal, but don't necessarily feel like they're worth the effort to create an individual JIRA issue on their own merits. Examples include things like "bring all the website docs up to date in preparation for release x.y.z" or "refactor this particular API into a separate Maven module" that will likely be executed as a series of discrete steps, but which can easily be tagged to such an omnibus issue. It's not just for the convenience of the release manager in collecting things for the release notes (although, as an RM, that feature is greatly appreciated! :-). It's also about encouraging changes that implement planned improvements (where the JIRA issues are used to plan out the roadmap, as well as to track bugs and RFEs). Craig regards,
Martin On 10/14/06, Matthias Wessendorf <[EMAIL PROTECTED]> wrote: > +1 (binding) > > On 10/14/06, Matthias Wessendorf <[EMAIL PROTECTED]> wrote: > > hi, > > > > in myfaces we have the sorta rule to create a jira issue for almost > > all commits. That has the benefit all of the ongoing *development* is > > more monitorable. I pretty much like that. Also it has the benefits > > for a thing called release note. just put all resolved jira numbers > > into the release note. > > > > What do you think? > > > > -- > > Matthias Wessendorf > > http://tinyurl.com/fmywh > > > > further stuff: > > blog: http://jroller.com/page/mwessendorf > > mail: mwessendorf-at-gmail-dot-com > > > > > -- > Matthias Wessendorf > http://tinyurl.com/fmywh > > further stuff: > blog: http://jroller.com/page/mwessendorf > mail: mwessendorf-at-gmail-dot-com > -- http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces
