From: Khem Raj <raj.khem@gmail.com>
To: musl@lists.openwall.com
Subject: Re: call it musl 1.2.0?
Date: Fri, 9 Aug 2019 08:30:03 -0700 [thread overview]
Message-ID: <CAMKF1srC7RDnYuA2dNsUGR+d0QxjvOXTsB9rHtDUEnGfp7JJoQ@mail.gmail.com> (raw)
In-Reply-To: <20190809054830.GG9017@brightrain.aerifal.cx>
On Thu, Aug 8, 2019 at 10:48 PM Rich Felker <dalias@libc.org> wrote:
>
> An idea crossed my mind today regarding the time64 conversion: should
> we call the first release with it switched over musl 1.2.0 instead of
> 1.1.25? This would both reflect that there's something ABI-significant
> (and a big functional milestone) about the release, and would admit
> keeping a 1.1.x branch around for a while with backports of any major
> bug fixes, since there will probably be some users hesitant to switch
> over to 64-bit time_t right away before it's well-tested.
>
I like the idea.
what do you think about 2.0
> Looking at the roadmap goals that were set for 1.2.0 a while (a couple
> years?) back now, most of them have been met:
>
> - Out-of-tree builds
> - Deduplication and cleanup of bits header system
> - Deduplication of atomic asm logic
> - AArch64 port
> - RISC-V 64 port
> - Significant improvement to previously-buggy/experimental archs
> - External _FORTIFY_SOURCE implementation available
> - External nss replacement available
> - Unicode (mostly?) up-to-date
>
> The ones that have not been met are:
>
> - Locale overhaul (lots of subpoints)
> - IDN support
> - All documentation goals
> - Midipix
>
> All except which are (to say the least) somewhat drawn-out goals with
> no end in sight.
>
> Adding "64-bit time_t on 32-bit archs" to the above completed list,
> and possibly also adding experimental riscv32, it sounds pretty
> 1.2.0-worthy to me.
>
> Thoughts on this?
>
> Rich
next prev parent reply other threads:[~2019-08-09 15:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-09 5:48 Rich Felker
2019-08-09 15:30 ` Khem Raj [this message]
2019-08-09 15:54 ` 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=CAMKF1srC7RDnYuA2dNsUGR+d0QxjvOXTsB9rHtDUEnGfp7JJoQ@mail.gmail.com \
--to=raj.khem@gmail.com \
--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).