Date: Tue, 12 May 2015 23:57:05 -0400 From: Rich Felker <dalias@...c.org> To: musl@...ts.openwall.com Subject: Post-1.1.9 roadmaps, towards 1.2 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
Powered by blists - more mailing lists
Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.