Hello Tom!
Are you saying that we should just leave them in RESOLVED or VERIFIED for
the sake of not generating extra emails? I don't think avoiding to generate
an email is that important.
The informative message should be when the issue goes from VERIFIED to
CLOSED so the step from RESOLVED to VERIFIED is the extra step generating an
email.
The extra value added by the tidyness is what Dave considered a problem,
i.e. that the issues are RESOLVED or VERIFIED and thus on someones
conscience. If we could just consider all issues equally closed whether they
are RESOLVED, VERIFIED or CLOSED then that wouldn't be a problem. I would
prefer to join these three states into a single one but the Tigris
infrastructure doesn't allow it.
I will do the 0.20 issues now to get the feel of how this will work.
/Linus
2008/9/21 Tom Morris <[EMAIL PROTECTED]>
> On Sun, Sep 21, 2008 at 5:02 AM, Linus Tolke <[EMAIL PROTECTED]> wrote:
>
> > I noticed that when using the "Change several issues at once"-function I
> was
> > not able to close Resolved issues so I had to verify them first. That is
> the
> > reason there were two mails per issue. I am not very eager to go through
> > issue per issue but anyone that wants can do that for old issues (0.20,
> > 0.22, or 0.24).
>
> In that case, I'm not sure it's worth the effort to get all issues
> closed just for the sake of "tidyness." Does it add any value to
> either the user or the development team?
>
> I think there is value to having the users know that their bug fixes
> are available in a stable release, but perhaps we could do that using
> some other mechanism if it's too awkward to do using the
> Tigris/Collabnet IssueZilla mechanisms.
>
> Tom
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
