From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/14878 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Rich Felker Newsgroups: gmane.linux.lib.musl.general Subject: Re: time64 switchover -- distro plans? Date: Sun, 27 Oct 2019 19:44:32 -0400 Message-ID: <20191027234432.GB16318@brightrain.aerifal.cx> References: <20191027040820.GV16318@brightrain.aerifal.cx> Reply-To: musl@lists.openwall.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="58893"; mail-complaints-to="usenet@blaine.gmane.org" User-Agent: Mutt/1.5.21 (2010-09-15) To: musl@lists.openwall.com Original-X-From: musl-return-14894-gllmg-musl=m.gmane.org@lists.openwall.com Mon Oct 28 00:44:47 2019 Return-path: Envelope-to: gllmg-musl@m.gmane.org Original-Received: from mother.openwall.net ([195.42.179.200]) by blaine.gmane.org with smtp (Exim 4.89) (envelope-from ) id 1iOsDH-000FEl-An for gllmg-musl@m.gmane.org; Mon, 28 Oct 2019 00:44:47 +0100 Original-Received: (qmail 5686 invoked by uid 550); 27 Oct 2019 23:44:45 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-ID: Original-Received: (qmail 5668 invoked from network); 27 Oct 2019 23:44:44 -0000 Content-Disposition: inline In-Reply-To: Original-Sender: Rich Felker Xref: news.gmane.org gmane.linux.lib.musl.general:14878 Archived-At: On Sun, Oct 27, 2019 at 09:19:07AM +0100, Khem Raj wrote: > On Sun, Oct 27, 2019 at 5:08 AM Rich Felker 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