struts-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paul Benedict" <pbened...@apache.org>
Subject Re: Resolving/Closing JIRA issues
Date Wed, 08 Aug 2007 02:02:39 GMT
Don, the PITA truth is the only reason why I use Resolved up to a release.
:-)

On 8/7/07, Don Brown <mrdon@twdata.org> wrote:
>
> My 2c is I don't see any practical value in resolved/closed.  They are
> functionally the same thing, only closed is a PITA because to change
> it, you have to reopen it.  I know many orgs have workflows where the
> two states mean very different things, but for Struts, I think it
> would be overkill.
>
> Still, if you want to do something like Paul, that's fine, but I
> probably won't for my tickets.
>
> Don
>
> On 8/8/07, Paul Benedict <pbenedict@apache.org> wrote:
> > I have been doing the same: resolving when finishing the issue and then
> > closing once the release is finished.
> >
> > On 8/7/07, Niall Pemberton <niall.pemberton@gmail.com> wrote:
> > >
> > > On 8/7/07, Antonio Petrelli <antonio.petrelli@gmail.com> wrote:
> > > > 2007/8/7, James Mitchell <jmitchtx@gmail.com>:
> > > > >
> > > > > That makes sense to me.  I don't remember what the decision was on
> > > > > that.  I think this has more to do with making the release
> managers
> > > > > life easier than policy per se.
> > > > >
> > > > > I can reopen and resolve if needed.
> > > >
> > > >
> > > > It wasn't an "accusation" for your particular issue. I've seen
> people
> > > > closing issues directly (probably at Commons) so maybe this is the
> > > correct
> > > > behaviour for Struts.
> > > > I think that a document should be prepared to inform all developers
> on
> > > the
> > > > correct steps to follow (whatever it is).
> > >
> > > The only comment I have is that closing issues before a release is a
> > > PITA if you use Jira for release notes - and want to make any changes
> > > (correct version number, change title etc) because if they're closed
> > > you first have to re-open before you can then edit.
> > >
> > > Niall
> > >
> > >
> > > > Ciao
> > > > Antonio
> > > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> > > For additional commands, e-mail: dev-help@struts.apache.org
> > >
> > >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message