+1 We basically decided on this a long time ago but not everyone is following it. Newer versions of JIRA (in use with Shale but not MyFaces) also allows you to disable email on bulk changes.
At some point I will change the JIRA workflow so that you can not directly close a feature (it must be resolved first.) This will help enforce the policy. Sean On 8/18/06, Bruno Aranda <[EMAIL PROTECTED]> wrote:
+1 I thought we were doing that already, Cheers, Bruno On 8/17/06, Cagatay Civici <[EMAIL PROTECTED]> wrote: > I totaly agree. > > Regards > > Cagatay > > > On 8/17/06, Mike Kienenberger <[EMAIL PROTECTED]> wrote: > > On 8/17/06, Mike Kienenberger <[EMAIL PROTECTED] > wrote: > > > Now that JIRA supports bulk operations, I'd like to propose that we > > > use the resolve status to identify things that are fixed, but not yet > > > available in a release. As part of the release process, we would > > > change all resolved issues for a snapshot to closed after the release > > > is made. > > > > Also, so long as every change is documented as a JIRA issue, these > > resolved issues can also be used to generate our release notes/change > > log for the release. > > > > So it's equally-important to have a JIRA issue for each change made. > > > >
