From: Joseph Myers <joseph@codesourcery.com>
To: Rafal Luzynski <digitalfreak@lingonborough.com>
Cc: Carlos O'Donell <carlos@redhat.com>, <libc-stable@sourceware.org>
Subject: Re: [PATCH 5/5] NEWS: Add entries for bugs: 22848, 22932, 22937, 22963.
Date: Mon, 01 Jan 2018 00:00:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.20.1803152109040.3226@digraph.polyomino.org.uk> (raw)
In-Reply-To: <689420158.50213.1521148010464@poczta.nazwa.pl>
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
next prev parent reply other threads:[~2018-03-15 21:10 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-01 0:00 [PATCH 0/5] Backport of fixes " Rafal Luzynski
2018-01-01 0:00 ` [PATCH 4/5] cs_CZ locale: Add alternative month names (bug 22963) Rafal Luzynski
2018-01-01 0:00 ` Carlos O'Donell
2018-01-01 0:00 ` Rafal Luzynski
2018-01-01 0:00 ` [PATCH 5/5] NEWS: Add entries for bugs: 22848, 22932, 22937, 22963 Rafal Luzynski
2018-01-01 0:00 ` Carlos O'Donell
2018-01-01 0:00 ` Rafal Luzynski
2018-01-01 0:00 ` Rafal Luzynski
2018-01-01 0:00 ` Carlos O'Donell
2018-01-01 0:00 ` Joseph Myers [this message]
2018-01-01 0:00 ` [PATCH v2 5/5][COMMITTED] " Rafal Luzynski
2018-01-01 0:00 ` [PATCH 5/5] " Joseph Myers
2018-01-01 0:00 ` Carlos O'Donell
2018-01-01 0:00 ` Joseph Myers
2018-01-01 0:00 ` [PATCH 1/5] ca_ES locale: Update LC_TIME (bug 22848) Rafal Luzynski
2018-01-01 0:00 ` Carlos O'Donell
2018-01-01 0:00 ` Rafal Luzynski
2018-01-01 0:00 ` [PATCH 2/5] lt_LT locale: Update abbreviated month names (bug 22932) Rafal Luzynski
2018-01-01 0:00 ` Carlos O'Donell
2018-01-01 0:00 ` Rafal Luzynski
2018-01-01 0:00 ` [PATCH 3/5] Greek (el_CY, el_GR) locales: Introduce ab_alt_mon (bug 22937) Rafal Luzynski
2018-01-01 0:00 ` Carlos O'Donell
2018-01-01 0:00 ` Rafal Luzynski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.20.1803152109040.3226@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=carlos@redhat.com \
--cc=digitalfreak@lingonborough.com \
--cc=libc-stable@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).