From: Petr Lautrbach <lautrbach@redhat.com>
To: James Carter <jwcart2@gmail.com>, Johannes Segitz <jsegitz@suse.de>
Cc: selinux@vger.kernel.org
Subject: Re: Where's 3.6-rc3 and plan with 3.6 release
Date: Mon, 11 Dec 2023 17:30:29 +0100 [thread overview]
Message-ID: <87il54snve.fsf@redhat.com> (raw)
In-Reply-To: <CAP+JOzRaEO91z1th-zfVi4-pNokJaQqXGDCKGyv=rz+5UWeRvg@mail.gmail.com>
James Carter <jwcart2@gmail.com> writes:
> On Mon, Dec 11, 2023 at 10:08 AM Johannes Segitz <jsegitz@suse.de> wrote:
>>
>> On Mon, Dec 11, 2023 at 01:47:16PM +0100, Petr Lautrbach wrote:
>> > I consider two options now - a) to release 3.6-rc3 on this Wednesday and
>> > leave 3.6 to the next year; b) to release directly 3.6 this Wednesday.
>>
>> I would be fine with b. In my experience there's not that much breakage and
>> the chance that a rc3 will uncover something significant seems small
>>
>
> I am fine with option b. The only reason I would want to delay would
> be for the prefix/suffix patches, but it seems like there might be
> more work required on the kernel side, so I don't think that they'll
> be ready for this release regardless.
>
OK
I'll release 3.6 on this Wednesday.
Thanks!
Petr
> Jim
>
>
>> Johannes
>> --
>> GPG Key EE16 6BCE AD56 E034 BFB3 3ADD 7BF7 29D5 E7C8 1FA0
>> Subkey fingerprint: 250F 43F5 F7CE 6F1E 9C59 4F95 BC27 DD9D 2CC4 FD66
>> SUSE Software Solutions Germany GmbH, Frankenstraße 146, 90461 Nürnberg, Germany
>> Geschäftsführer: Ivo Totev, Andrew McDonald, Werner Knoblich (HRB 36809, AG Nürnberg)
prev parent reply other threads:[~2023-12-11 16:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-11 12:47 Where's 3.6-rc3 and plan with 3.6 release Petr Lautrbach
2023-12-11 15:07 ` Johannes Segitz
2023-12-11 15:29 ` James Carter
2023-12-11 16:30 ` Petr Lautrbach [this message]
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=87il54snve.fsf@redhat.com \
--to=lautrbach@redhat.com \
--cc=jsegitz@suse.de \
--cc=jwcart2@gmail.com \
--cc=selinux@vger.kernel.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).