From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Post-1.1.9 roadmaps, towards 1.2
Date: Tue, 12 May 2015 23:57:05 -0400 [thread overview]
Message-ID: <20150513035705.GA19045@brightrain.aerifal.cx> (raw)
I updated the wiki roadmap page to:
= musl 1.1.10 =
Estimated release: June
Primary targets:
* Resolving GCC symbol-versioning incompatibility issue - see
http://www.openwall.com/lists/musl/2015/05/10/1
* Auto-generation of CFI directives for asm sources - see
http://www.openwall.com/lists/musl/2015/05/12/3
* Enhanced LSB/glibc ABI-compat, especially fortify __*_chk symbols
* New getlogin[_r] with lookup via controlling tty
Secondary targets:
* Many cleanup tasks - see
http://www.openwall.com/lists/musl/2015/05/02/1
* Some remaining pending patches - see
http://www.openwall.com/lists/musl/2015/04/28/5
* Remapping of glibc-ABI-incompatible symbols (regexec, etc.) by
dynamic linker
= musl 1.1.11 =
Estimated release: July
Primary targets:
* LC_COLLATE implementation
* IDN support in DNS resolver
* Message translation support for dynamic linker
As usual this can be shuffled around. I feel like the above items
would put us in a good position for 1.2.0 as the next release,
hopefully with just a few minor bug fixes. Of course there are also
out-of-tree things I want for 1.2:
* Non-glibc-based nscd-protocol backend for LDAP (and perhaps NIS)
* Locale data and libc message translations
* External header-file-only fortify library providing _FORTIFY_SOURCE
feature
* Major documentation update/additions
* New website at musl.libc.org
I believe the fortify stuff is basically done (Alpine is using it) but
other items are still unstarted or in very early stages.
Rich
reply other threads:[~2015-05-13 3:57 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20150513035705.GA19045@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).