Great idea Tom!
There are two problem with this.
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).
I, or the person doing releases, have to remember to do this. I will write
instructions in the Cookbook to help me remembering.
/Linus
2008/9/20 Tom Morris <[EMAIL PROTECTED]>
> On Fri, Sep 12, 2008 at 6:28 PM, Dave Thompson <[EMAIL PROTECTED]> wrote:
>
> > I suppose when I see 1000s of issues to be verified, I mentally calculate
> > 20mins per issue * 1000, which is equivalent to approx 2 months of a full
> > time job. Anyone can get a lot done in 2 months.
> >
> > My suggestions are:
> ...
>
> > 3) Send an automatic message out to every resolved issue when we do a
> major
> > stable release, stating something like "This issue has been marked as
> > resolved in time for release X. If nobody objects by reopenning this
> issue,
> > is will be automatically closed [in 2 days' time / in 2 months' time /
> > shortly before the next stable release]."
> >
> > 4) Close resolved issues that have not been re-openned after the period
> > stated in 3).
>
> I think we should a) minimize the number of emails and b) have the
> emails provide useful information to the user.
>
> Can't we combine these two steps by closing the issues by default and
> having the message say something to the effect of "The fix for this
> issue was included in release 1.5. You can download this release from
> <URL>. If there is a still a problem, please reopen this issue and
> update it with any new information."
>
> Tom
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
