Closing fixed bugs

[Neil Skrypuch]

On Saturday 14 February 2009, Dan Kegel wrote:
> A few months ago, Alexandre started including lists of fixed
> bugs in his release announcements.
> See e.g. http://www.winehq.org/announce/1.1.15, which  says
>
> Bugs fixed in 1.1.15:
>    5694  Lionhead Black & White 2 demo crashes
>    7014  Unhandled page fault when exiting Commandos - BEL
>    7297  MIDI in/out fails, ports recognized
> ...
>
> I rather like those lists.  He generates them by simply querying
> for open but fixed bugs right when he does the release;
> he then closes the bugs.  They're good for PR if nothing else.
>
> For this to work, we have to let Alexandre be the only person
> to close fixed bugs.  (Of course, it's ok for other people to
> mark bugs fixed, and it's ok for anyone to close invalid or dup bugs.)
> If anybody else closes a fixed bug, it won't show up in the
> list of fixed bugs for any release.
>
> A corner case is when a bug is marked fixed sometime
> after release.  I think it's ok to leave it for Alexandre to
> close; that way it shows up in at least one release announcement.
> Even if it shows up a few releases late, that's better than not
> showing up at all.
>
> Sound reasonable?
>
> I ask because Vitaliy closed http://bugs.winehq.org/show_bug.cgi?id=10923
> even after I tried to explain this to him, so I figured it
> needed a wider discussion.
> - Dan

Couldn't you just query Bugzilla for all the bugs closed between $release and 
$lastrelease?

- Neil