public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Andreas K. Huettel" <dilfridge@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] glibc-2.26 stabilization soon
Date: Sun, 13 May 2018 23:32:34 +0200	[thread overview]
Message-ID: <2912206.2o2N4qEmej@pinacolada> (raw)

[-- Attachment #1: Type: text/plain, Size: 1061 bytes --]

The number of blocker bugs has decreased a lot, so unless something both new 
and serious is coming up I'm going to ask for glibc-2.26 stabilization on
   6/June/2018 
(that is a month after uploading the latest patchset). We really need to get 
this rolling, since the glibc-2.28 release is already approaching. 

If you still have glibc-2.26 related bugs for your packages, please have a 
look at the following link, and contact me if you encounter unsolvable 
problems.

https://wiki.gentoo.org/wiki/Project:Toolchain#glibc-2.26

The biggest trend in the blockers seems to be a delay in ppc stabilizations.

2.27 will be rekeyworded when 2.26 is stable. The impact of 2.27 and 2.28 will 
hopefully be smaller, since then we've successfully made the RPC transition, 
and since these releases contain less breaking changes.

2.25 and earlier will remain available, but be masked because of unresolved 
security issues.

-- 
Andreas K. Hüttel
dilfridge@gentoo.org
Gentoo Linux developer
(council, toolchain, perl, libreoffice, comrel)

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 981 bytes --]

                 reply	other threads:[~2018-05-13 21:32 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=2912206.2o2N4qEmej@pinacolada \
    --to=dilfridge@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.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