Proposal: Mark fixed issues as resolved instead of closed -- close all resolved issues on release

[Mike Kienenberger <mk...@gmail.com>]

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.

Re: Proposal: Mark fixed issues as resolved instead of closed -- close all resolved issues on release

[Martin Marinschek <ma...@gmail.com>]

sounds good to me!

regards,

Martin

On 8/17/06, Mike Kienenberger <mk...@gmail.com> 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.
>


-- 

http://www.irian.at

Your JSF powerhouse -
JSF Consulting, Development and
Courses in English and German

Professional Support for Apache MyFaces

Re: Proposal: Mark fixed issues as resolved instead of closed -- close all resolved issues on release

[Matthias Wessendorf <ma...@apache.org>]

sounds reasonalbe.

On 8/17/06, Mike Kienenberger <mk...@gmail.com> 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.
>


-- 
Matthias Wessendorf

further stuff:
blog: http://jroller.com/page/mwessendorf
mail: mwessendorf-at-gmail-dot-com

Re: Proposal: Mark fixed issues as resolved instead of closed -- close all resolved issues on release

[Mike Kienenberger <mk...@gmail.com>]

I see the primary use of resolved versus closed as keeping/generating
a log of what's changed during a release.  Things that don't impact a
release (non-fixes) don't need to have a resolved state.

I have never had a need to revisit an invalid issue.  Won't fix hasn't
come up yet.

Users can already reopen closed issues.  Even if they couldn't, a
comment posted to the issue (or the mailing list) would have me reopen
an issue.


On 8/20/06, Sean Schofield <se...@gmail.com> wrote:
> > Can you do it so this is only required for Fixed issues?
> > Invalid/Won't Fix issues should be closed directly.
>
> Why should these be closed directly?  Maybe we would revisit one of
> these before the release is done.  Also, I believe having them
> resolved (instead of closed) allows the user to appeal and reopen.
> Just some thoughts ...
>
> Sean
>

Re: Proposal: Mark fixed issues as resolved instead of closed -- close all resolved issues on release

[Sean Schofield <se...@gmail.com>]

> Can you do it so this is only required for Fixed issues?
> Invalid/Won't Fix issues should be closed directly.

Why should these be closed directly?  Maybe we would revisit one of
these before the release is done.  Also, I believe having them
resolved (instead of closed) allows the user to appeal and reopen.
Just some thoughts ...

Sean

Re: Proposal: Mark fixed issues as resolved instead of closed -- close all resolved issues on release

[Mike Kienenberger <mk...@gmail.com>]

On 8/20/06, Sean Schofield <se...@gmail.com> wrote:
> 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.

Can you do it so this is only required for Fixed issues?
Invalid/Won't Fix issues should be closed directly.

Re: Proposal: Mark fixed issues as resolved instead of closed -- close all resolved issues on release

[Sean Schofield <se...@gmail.com>]

+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 <br...@gmail.com> wrote:
> +1 I thought we were doing that already,
>
> Cheers,
>
> Bruno
>
> On 8/17/06, Cagatay Civici <ca...@gmail.com> wrote:
> > I totaly agree.
> >
> > Regards
> >
> > Cagatay
> >
> >
> > On 8/17/06, Mike Kienenberger <mk...@gmail.com> wrote:
> > > On 8/17/06, Mike Kienenberger <mkienenb@gmail.com > 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.
> > >
> >
> >
>

Re: Proposal: Mark fixed issues as resolved instead of closed -- close all resolved issues on release

[Bruno Aranda <br...@gmail.com>]

+1 I thought we were doing that already,

Cheers,

Bruno

On 8/17/06, Cagatay Civici <ca...@gmail.com> wrote:
> I totaly agree.
>
> Regards
>
> Cagatay
>
>
> On 8/17/06, Mike Kienenberger <mk...@gmail.com> wrote:
> > On 8/17/06, Mike Kienenberger <mkienenb@gmail.com > 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.
> >
>
>

Re: Proposal: Mark fixed issues as resolved instead of closed -- close all resolved issues on release

[Cagatay Civici <ca...@gmail.com>]

I totaly agree.

Regards

Cagatay

On 8/17/06, Mike Kienenberger <mk...@gmail.com> wrote:
>
> On 8/17/06, Mike Kienenberger <mk...@gmail.com> 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.
>

Re: Proposal: Mark fixed issues as resolved instead of closed -- close all resolved issues on release

[Mike Kienenberger <mk...@gmail.com>]

On 8/17/06, Mike Kienenberger <mk...@gmail.com> 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.