[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH 5/5] NEWS: Add entries for bugs: 22848, 22932, 22937, 22963.
On Thu, 15 Mar 2018, Rafal Luzynski wrote:
> > Not marked fixed in 2.28 (target milestone should be set to 2.28 and marked
> > fixed).
>
> I was going to ask if it should be marked as fixed in 2.28 or 2.27.1
> (there is no such option in Bugzilla) or 2.27. Also I was going to mark
> as fixed after pushing to 2.27. The same about other bugs.
The milestone is always about mainline releases, not subsequent fixes on
release branches.
Bugs should always be marked as FIXED as soon as the fix is on mainline,
so that list-fixed-bugs.py always generates a correct list of the bugs
that would be fixed in the next release if we were to release immediately.
--
Joseph S. Myers
joseph@codesourcery.com
- References:
- [PATCH 0/5] Backport of fixes for bugs: 22848, 22932, 22937, 22963.
- From: Rafal Luzynski <digitalfreak@lingonborough.com>
- [PATCH 5/5] NEWS: Add entries for bugs: 22848, 22932, 22937, 22963.
- From: Rafal Luzynski <digitalfreak@lingonborough.com>
- Re: [PATCH 5/5] NEWS: Add entries for bugs: 22848, 22932, 22937, 22963.
- From: Carlos O'Donell <carlos@redhat.com>
- Re: [PATCH 5/5] NEWS: Add entries for bugs: 22848, 22932, 22937, 22963.
- From: Rafal Luzynski <digitalfreak@lingonborough.com>
- Prev by Date:
Re: [PATCH 5/5] NEWS: Add entries for bugs: 22848, 22932, 22937, 22963.
- Next by Date:
Re: [PATCH 5/5] NEWS: Add entries for bugs: 22848, 22932, 22937, 22963.
- Previous by thread:
Re: [PATCH 5/5] NEWS: Add entries for bugs: 22848, 22932, 22937, 22963.
- Next by thread:
Re: [PATCH 5/5] NEWS: Add entries for bugs: 22848, 22932, 22937, 22963.
- Index(es):