From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/4060 Path: news.gmane.org!not-for-mail From: Rich Felker Newsgroups: gmane.linux.lib.musl.general Subject: musl 0.9.14 released Date: Tue, 24 Sep 2013 02:18:49 -0400 Message-ID: <20130924061849.GA3027@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 1380003540 26572 80.91.229.3 (24 Sep 2013 06:19:00 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 24 Sep 2013 06:19:00 +0000 (UTC) To: musl@lists.openwall.com Original-X-From: musl-return-4064-gllmg-musl=m.gmane.org@lists.openwall.com Tue Sep 24 08:19:04 2013 Return-path: Envelope-to: gllmg-musl@plane.gmane.org Original-Received: from mother.openwall.net ([195.42.179.200]) by plane.gmane.org with smtp (Exim 4.69) (envelope-from ) id 1VOLxg-0003qs-6A for gllmg-musl@plane.gmane.org; Tue, 24 Sep 2013 08:19:04 +0200 Original-Received: (qmail 20410 invoked by uid 550); 24 Sep 2013 06:19:03 -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 20402 invoked from network); 24 Sep 2013 06:19:02 -0000 Content-Disposition: inline User-Agent: Mutt/1.5.21 (2010-09-15) Xref: news.gmane.org gmane.linux.lib.musl.general:4060 Archived-At: Hi, Earlier today I posted the release of musl 0.9.14: The result of major bug-hunting. Fixes a regression in installation of the dynamic linker symlink when DESTDIR is used, rare deadlock in libc-internal locking, incorrect dynamic linker fallback to built-in search paths in certain error cases, popen failures when the caller has closed stdin or stdout, deadlock and memory-corruption issues in multi-threaded set*id and setrlimit operations, and multiple low-impact bugs in math functions and other components. http://www.etalabs.net/musl/releases/musl-0.9.14.tar.gz This release was a little later than I would have preferred; I had hoped to release it last weekend, but held off for a bit while we tracked down some additional bugs and potential-bugs. This has put the roadmap for 1.0 a little bit behind, but the bright side is that we found and fixed a lot of bugs, including some that had been elusive for a long time. I still think we should have one more release, 0.9.15, before calling this 1.0. My intent is to continue the bug-hunting, based on an approach of: - Writing and running more test. - Source level analysis (grepping, static analysis, etc.). - Tracking down application build failures and any mysterious runtime problems in applications. I'll continue working on the documentation too, in hopes of including a presentable version in the next release tarball so it can get some public review before 1.0. At this point my leaning is to hold off on any other functional changes aside from bug fixes before 1.0; there were a few items on the Roadmap as secondary targets which would have been nice, but they're not critical and stabilizing for 1.0 is more important. Sometime soon I also want to focus on what the development and release model post-1.0 will be, especially whether we'll aim to maintain a 'stable' branch with minimal new features alongside new development. Rich