public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: "Dmitry V. Levin" <ldv@altlinux.org>
To: libc-alpha@sourceware.org
Subject: glibc 2.27: less than two weeks till release
Date: Thu, 18 Jan 2018 17:56:00 -0000	[thread overview]
Message-ID: <20180118175601.GC31922@altlinux.org> (raw)

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

Hi,

We have less than two weeks till the planned release date.  By this date
in the freeze calendar we should have been ready to start architecture
testing for 2.27, but, unfortunately, with pending complicated patches
that affect all architectures we cannot really start the testing until
these patches have either been accepted or postponed to 2.28.
Nevertheless, architecture maintainers are encouraged to do preliminary
testing.

Here is a recap of pending issues.

* Release blockers listed in the release page[1]:

** Reported failure on Intel hardware involving steam/mono runtimes[2],
likely a regression caused by recent setjmp changes[3].

There is going to be an ABI change if we have to revert these changes,
hampering the pre-release testing.
H.J., is there any progress with this?

** Month names in alternative grammatical case[4]

This has already been reviewed by Carlos.
Rafal, is there anything that has to be done before these series is committed?

** Review / update collation data from Unicode / ISO 14651[5]

Given that the bug is almost 6 year old and no patch has been submitted
for review yet, does it have any chance for a review and a proper testing
before the release?
Mike, why do you consider this change as a blocker for 2.27?

* Features listed as desirable in the release page:

** C11 threads[6]

This has been waiting for review for many weeks, last week Carlos said
he will review this.
It's unfortunate that we still have complicated all-arch patch series
like this still pending review for 2.27.

** Istvan Kurucsai's malloc security patches[7]

This series has been under review for many weeks.
Florian, is it still targeted for 2.27?

** RISC-V port v4[8]

There is a separate summary[9] on this topic.

** Don't include libio.h from the installed stdio.h[10]

This is still pending review for 2.27.
Florian, anyone else, is there any progress with this?

[1] https://sourceware.org/glibc/wiki/Release/2.27
[2] https://sourceware.org/ml/libc-alpha/2018-01/msg00178.html
[3] https://sourceware.org/ml/libc-alpha/2018-01/msg00268.html
[4] https://sourceware.org/ml/libc-alpha/2018-01/msg00258.html
[5] https://sourceware.org/bugzilla/show_bug.cgi?id=14095
[6] https://sourceware.org/ml/libc-alpha/2017-09/msg00871.html
[7] https://sourceware.org/ml/libc-alpha/2017-11/msg00229.html
[8] https://sourceware.org/ml/libc-alpha/2018-01/msg00475.html
[9] https://sourceware.org/ml/libc-alpha/2018-01/msg00379.html
[10] https://sourceware.org/ml/libc-alpha/2018-01/msg00248.html


-- 
ldv

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 801 bytes --]

             reply	other threads:[~2018-01-18 17:56 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-18 17:56 Dmitry V. Levin [this message]
2018-01-18 21:56 ` TODO: Alternative month names (was: Re: glibc 2.27: less than two weeks till release) Rafal Luzynski
2018-01-18 22:04   ` Zack Weinberg
2018-01-18 23:07     ` Rafal Luzynski
2018-01-19  8:51   ` TODO: Alternative month names Carlos O'Donell
2018-01-19 10:41     ` Rafal Luzynski
2018-01-19  8:54 ` glibc 2.27: less than two weeks till release Carlos O'Donell
2018-01-21 22:01 ` Romain Naour
2018-01-22 11:11   ` Szabolcs Nagy
2018-01-22 11:53     ` Adhemerval Zanella
2018-01-22 12:08       ` Szabolcs Nagy
2018-01-22 15:49     ` Joseph Myers
2018-01-22 16:00       ` Florian Weimer
2018-01-22 15:45   ` Joseph Myers
2018-01-24 21:57     ` Romain Naour
2018-01-24 22:02       ` Joseph Myers
2018-01-28 17:35         ` Romain Naour
2018-01-29 20:30           ` Joseph Myers
2018-01-30  0:21             ` Romain Naour
2018-01-30  1:01               ` Joseph Myers

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=20180118175601.GC31922@altlinux.org \
    --to=ldv@altlinux.org \
    --cc=libc-alpha@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).