From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/7016 Path: news.gmane.org!not-for-mail From: Rich Felker Newsgroups: gmane.linux.lib.musl.general Subject: What would make musl 1.2? Date: Fri, 13 Feb 2015 02:46:03 -0500 Message-ID: <20150213074603.GA975@brightrain.aerifal.cx> Reply-To: musl@lists.openwall.com NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1423813581 27379 80.91.229.3 (13 Feb 2015 07:46:21 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 13 Feb 2015 07:46:21 +0000 (UTC) To: musl@lists.openwall.com Original-X-From: musl-return-7029-gllmg-musl=m.gmane.org@lists.openwall.com Fri Feb 13 08:46:21 2015 Return-path: Envelope-to: gllmg-musl@m.gmane.org Original-Received: from mother.openwall.net ([195.42.179.200]) by plane.gmane.org with smtp (Exim 4.69) (envelope-from ) id 1YMAxA-00050w-Px for gllmg-musl@m.gmane.org; Fri, 13 Feb 2015 08:46:20 +0100 Original-Received: (qmail 5732 invoked by uid 550); 13 Feb 2015 07:46:19 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Original-Received: (qmail 5697 invoked from network); 13 Feb 2015 07:46:15 -0000 Content-Disposition: inline User-Agent: Mutt/1.5.21 (2010-09-15) Original-Sender: Rich Felker Xref: news.gmane.org gmane.linux.lib.musl.general:7016 Archived-At: We're far enough along in the 1.1.x series now that I'd like to start thinking about what milestones might justify calling a release 1.2.0. Looking at the Open Issues and Roadmap on the wiki, the big things musl could gain in the near future look to be: - Finishing up all the loose ends on locale and multilingual support: IDN, message translations, iconv improvements, collation, and possibly the byte-based C locale. - Hardening/security features. - C++11 non-POD TLS. - Alternate user/group db backends (hopefully in upcoming 1.1.7). Any or all of these could become part of the wishlist for 1.2. Aside from those big functionality areas though, I think archs/porting might be one of the most important things to think about. Supporting aarch64 is definitely important in the near future, and it could be a big publicity boost. So could getting coverage for the remaining archs uClibc has that musl doesn't, or at least the ones of modern interest. Other ideas? Rich