mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Rich Felker <dalias@aerifal.cx>
To: musl@lists.openwall.com
Subject: musl 0.9.14 released
Date: Tue, 24 Sep 2013 02:18:49 -0400	[thread overview]
Message-ID: <20130924061849.GA3027@brightrain.aerifal.cx> (raw)

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


             reply	other threads:[~2013-09-24  6:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-24  6:18 Rich Felker [this message]
2013-09-24 13:51 ` John Spencer
2013-09-24 14:10   ` Luca Barbato
2013-09-24 17:22     ` Rich Felker
2013-09-24 19:13       ` Luca Barbato

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=20130924061849.GA3027@brightrain.aerifal.cx \
    --to=dalias@aerifal.cx \
    --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).