[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130629235041.GA5046@brightrain.aerifal.cx>
Date: Sat, 29 Jun 2013 19:50:41 -0400
From: Rich Felker <dalias@...ifal.cx>
To: musl@...ts.openwall.com
Subject: Proposed roadmap to 1.0
Hi all,
Here is a VERY tentative, proposed roadmap towards a 1.0 release of
musl. Comments welcome!
Rich
0.9.11
Projected release: ASAP
No further goals at the moment except fixing additional bugs found.
0.9.12
Projected release: Mid to late July
Key targets:
- Overhaul of time handling, including zoneinfo support.
- Overhaul resolver to better provide legacy APIs without code dup.
- Hybrid automatic/manual audit for cruft and code smells.
- Resolve symlink direction issue for dynamic linker.
- Affinity/cpuset interfaces.
0.9.13
Projected release: Early August
Key targets:
- Full C++ ABI compatibility with glibc/LSB.
- Support for all remaining iconv charsets of interest (KR/TW/HK).
- Possible overhaul of iconv for performance and clarity/simplicity.
- Possibly add stateful iconv support.
- Establish formal procedure for regression testing.
0.9.14
Projected release: End of summer
Key targets:
- Complete documentation draft.
- Performance testing on under-tested archs, fixing bottlenecks hit.
- Review for gratuitous application breakage (anything that could be
fixed with trivial changes that don't hurt musl's quality).
1.0.0
Projected release: Early fall
Key targets:
- Polished documentation.
- Organized and coordinated publicity plan.
- At least one new exciting addition to make the release noteworthy,
but which has no chance of breaking things that work. Best candidate
would be one or more new ports, labeled experimental.
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.
