[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140410024045.GA6538@brightrain.aerifal.cx>
Date: Wed, 9 Apr 2014 22:40:45 -0400
From: Rich Felker <dalias@...ifal.cx>
To: musl@...ts.openwall.com
Subject: Preparing for releases 1.1.0 and 1.0.1
I believe all of the key targets for 1.1.0 have been met, and we also
have fixed several bugs of sufficient severity that a maintenance
release to the 1.0 series is called for.
The commits which I plan to cherry-pick into the 1.0.1 release are:
30c1205acd73c8481ca34f0a41de1d41884d07b5
0a8d98285f46f721dabf38485df916c02d6a4675
91d5aa06572d2660122f9a06ed242fef0383f292
109048e031f39fbb370211fde44ababf6c04c8fb
89740868c9f1c84b8ee528468d12df1fa72cd392
e94d0692864ecf9522fd6a97610a47a2f718d3de
6fbdeff0e51f6afc38fbb1476a4db81322779da4
Note that 5446303328adf4b4e36d9fba21848e6feb55fab4, the malloc brk
exhaustion issue, is not yet in the list. While I'm doubtful that it
has any serious problems, I'd rather get it some more exposure before
putting it into the maintenance-only stable branch.
(BTW, does anyone with git expertise know how I can make git
cherry-pick -x skip a line before the "(cherry picked...)" message?
Perhaps there's a config option or a hook I could use?)
Things I could use help from volunteers on are:
- Reviewing changes, especially the above commits, to make sure they
don't have any stupid mistakes.
- Running tests and reporting any test regressions.
- Testing x32 and/or sh ports to determine if they're of sufficient
quality to promote up from "experimental" to the list of officially
supported archs.
- Informing me of any pending patches or trivial fix requests I might
have misplaced that could be committed before release.
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.
