From: Carlos O'Donell <carlos@redhat.com>
To: "Dmitry V. Levin" <ldv@altlinux.org>,
Rafal Luzynski <digitalfreak@lingonborough.com>
Cc: libc-stable@sourceware.org
Subject: Re: [2.27 COMMITTED] NEWS: add entries for bugs 17343, 20419, 22644, 22786, 22884, 22947, 23005, 23037, 23069, 23137
Date: Mon, 01 Jan 2018 00:00:00 -0000 [thread overview]
Message-ID: <e165323c-fc4f-711f-036a-63645308d0dd@redhat.com> (raw)
In-Reply-To: <20180511122612.GB480@altlinux.org>
On 05/11/2018 08:26 AM, Dmitry V. Levin wrote:
> On Fri, May 11, 2018 at 01:02:10PM +0200, Rafal Luzynski wrote:
>> Dmitry,
>>
>> Does this batch of backported bugfixes mean that you are
>> preparing for 2.27.1 official release, maybe today? If yes
>> then please also accept my recent patch. [1][2] It's trivial and
>> would be nice to have it backported. I will appreciate if you
>> commit it for me since I'm out of time atm.
>
> I don't think we are going to cut releases from 2.27 branch,
> but I don't mind backporting your fix now rather than later.
There is no official point release process.
We expect the distros to sync from the release branch if they want
the latest fixes.
We only produce official minor releases e.g. 2.28, and even then
just to provide official tarballs for projects that still follow
that kind of process (it helps our logical process flow forward
in a time boxed fasion with useful names for groups of changes).
--
Cheers,
Carlos.
next prev parent reply other threads:[~2018-05-11 12:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-01 0:00 Dmitry V. Levin
2018-01-01 0:00 ` Rafal Luzynski
2018-01-01 0:00 ` Dmitry V. Levin
2018-01-01 0:00 ` Carlos O'Donell [this message]
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=e165323c-fc4f-711f-036a-63645308d0dd@redhat.com \
--to=carlos@redhat.com \
--cc=digitalfreak@lingonborough.com \
--cc=ldv@altlinux.org \
--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).