From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Re: time64 switchover -- distro plans?
Date: Sun, 27 Oct 2019 19:44:32 -0400 [thread overview]
Message-ID: <20191027234432.GB16318@brightrain.aerifal.cx> (raw)
In-Reply-To: <CAMKF1spRjvha7c0dGwnvQO5tuNwm+JGcgGt9WM_Sjqf54C8EaQ@mail.gmail.com>
On Sun, Oct 27, 2019 at 09:19:07AM +0100, Khem Raj wrote:
> On Sun, Oct 27, 2019 at 5:08 AM Rich Felker <dalias@libc.org> wrote:
>
> > This thread is a call for feedback from distros (or other
> > similarly-situated systems integrators) using musl with 32-bit archs.
> > Everything is moving smoothly on my side for upcoming time64
> > switchover which will be included in the next release, 1.2.0. But with
> > this involving ABI issues between packages and changes that some
> > software may not be ready for, it will likely be at least somewhat
> > disruptive to distros/users.
>
>
> When are we planning for 1.2 release approximately?
> I would like to see it before March 2020 since openembedded/yocto releases
> in April this fits well with scheduling this upgrade and gives time to test
> it on various platforms
Absolutely before then, even if release plans slip far more than
usual. My hope right now is to keep up with the roadmap on the wiki
which has it at an unspecified time in November (2019, of course, but
clarifying which year since this is an ongoing joke about something on
#musl.. :). I will probably drop out some of the other goals from the
roadmap though to keep it focused and keep this on time.
> > In particular:
> >
> > * Are there resources I could/should make available that will help
> > things go smoothly?
> >
> > * Are you available for testing building and running packages against
> > time64 musl prior to release?
>
> Yes
Great!
> > From my side, I'm planning to write up release notes/announcement far
> > more detailed than usual, with instructions on switchover, what ABI
> > compatibility/stability does & doesn't mean, possible pitfalls, tips
> > for catching code that may have time64-related bugs, etc., and just
> > basic FAQ items like whether you need a 5.1+ kernel (no) or kernel
> > headers (no).
> >
> > I'll also be building and testing some software on i386 and sh at
> > least; I already started with busybox, which just got the main
> > time64-readiness issue I was aware of fixed.
> >
> > I think I'll push the last of the time64 patches within the next week,
> > possibly sooner, meaning "distros start testing" is a thing that could
> > begin really soon if anyone's up for it.
>
> I will be able to start doing master work in couple of weeks
Sounds like a good timeframe. time64 switchover will be upstream then
and it gives us a couple weeks to keep the subsequent release
in-month.
Rich
next prev parent reply other threads:[~2019-10-27 23:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-27 4:08 Rich Felker
2019-10-27 8:19 ` Khem Raj
2019-10-27 23:44 ` Rich Felker [this message]
2019-10-28 11:52 ` A. Wilcox
2019-10-29 17:05 ` Rich Felker
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=20191027234432.GB16318@brightrain.aerifal.cx \
--to=dalias@libc.org \
--cc=musl@lists.openwall.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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 NNTP newsgroup(s).