From: Johannes Segitz <jsegitz@suse.de>
To: Petr Lautrbach <lautrbach@redhat.com>
Cc: selinux@vger.kernel.org
Subject: Re: Where's 3.6-rc3 and plan with 3.6 release
Date: Mon, 11 Dec 2023 16:07:57 +0100 [thread overview]
Message-ID: <ZXclzTjExZpvWrew@suse.com> (raw)
In-Reply-To: <87o7ewsy7f.fsf@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 701 bytes --]
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
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)
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-12-11 15:08 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 [this message]
2023-12-11 15:29 ` James Carter
2023-12-11 16:30 ` Petr Lautrbach
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=ZXclzTjExZpvWrew@suse.com \
--to=jsegitz@suse.de \
--cc=lautrbach@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.