From: Carlos O'Donell <carlos@redhat.com>
To: GNU C Library <libc-alpha@sourceware.org>,
Tulio Magno Quites Machado Filho <tuliom@linux.vnet.ibm.com>,
Bill Schmidt <wschmidt@us.ibm.com>
Subject: glibc 2.28 release on August 1st and extended ABI freeze for ppc64le float128.
Date: Tue, 26 Jun 2018 19:32:00 -0000 [thread overview]
Message-ID: <4db8730d-158c-67e4-b4fd-55b3cc9a7100@redhat.com> (raw)
Community,
The next release of glibc 2.28 is planned for August 1st.
We normally enter a global ABI/API slushy freeze on July 1st.
Both IBM and Red Hat have a strong desire to see the IBM ppc64le
transition to the new long double format without having to wait an
additional 6 months until we have another release.
For example I want these changes in Fedora 29 so we can showcase the
latest IBM POWER9 hardware.
I'm willing to extend the ABI/API freeze to July 13th for the ppc64le
float128 changes, to allow those to go into the glibc 2.28 release.
This would leave us with 2 weeks of testing for most arches, and I
can make sure we get good testing coverage during those two weeks from
the set of hardware Red Hat has access to, and the Red Hat glibc team
doing builds and tests on x864_64, i686, ppc64be, ppc64le, s390, s390x,
armv7hl, and aarch64.
I'm not suggesting we move the August 1st release, but just decrease
the window of the ABI/API freeze, and restrict it to only the changes
we accept as such e.g. ppc64le float128 changes.
Does anyone object to this?
Cheers,
Carlos.
next reply other threads:[~2018-06-26 19:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-26 19:32 Carlos O'Donell [this message]
2018-06-26 19:35 ` Florian Weimer
2018-06-26 19:43 ` Tulio Magno Quites Machado Filho
2018-06-26 20:52 ` Joseph Myers
2018-06-27 2:00 ` Tulio Magno Quites Machado Filho
2018-06-29 14:33 ` Szabolcs Nagy
2018-06-29 14:36 ` Florian Weimer
2018-06-29 15:37 ` Szabolcs Nagy
2018-07-02 13:59 ` Maciej W. Rozycki
2018-07-02 15:22 ` Joseph Myers
2018-07-02 15:40 ` Maciej W. Rozycki
2018-07-03 13:53 ` Carlos O'Donell
2018-07-04 19:35 ` Tulio Magno Quites Machado Filho
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=4db8730d-158c-67e4-b4fd-55b3cc9a7100@redhat.com \
--to=carlos@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=tuliom@linux.vnet.ibm.com \
--cc=wschmidt@us.ibm.com \
/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).