This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: RFC: automatically listing fixed bugs for NEWS
- From: Joseph Myers <joseph at codesourcery dot com>
- To: Siddhesh Poyarekar <sid at reserved-bit dot com>
- Cc: <libc-alpha at sourceware dot org>, <lpsolit at gmail dot com>
- Date: Wed, 4 Nov 2015 21:26:15 +0000
- Subject: Re: RFC: automatically listing fixed bugs for NEWS
- Authentication-results: sourceware.org; auth=none
- References: <alpine dot DEB dot 2 dot 10 dot 1510291644120 dot 10299 at digraph dot polyomino dot org dot uk> <563A548D dot 6070507 at reserved-bit dot com>
On Thu, 5 Nov 2015, Siddhesh Poyarekar wrote:
> > * It would become important that people do actually set milestones when
> > closing bugs as fixed. Thus, people watching commits and Bugzilla should
> > watch for that.
>
> I wonder if bugzilla has some hidden field that stores the next release
> number so that if it is closed without a set milestone, it defaults to
> the next one. It then becomes the responsibility of the release manager
> to bump that bugzilla value on release.
Frédéric, is there such a feature in Bugzilla to set a default milestone
automatically whenever a bug (in glibc product in sourceware Bugzilla, not
for any other product there) is resolved as FIXED (such that the release
manager can then edit the default milestone when making a new release)?
--
Joseph S. Myers
joseph@codesourcery.com