mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Rich Felker <dalias@aerifal.cx>
To: musl@lists.openwall.com
Subject: Re: Proposed roadmap to 1.0
Date: Sat, 29 Jun 2013 23:01:50 -0400	[thread overview]
Message-ID: <20130630030150.GO29800@brightrain.aerifal.cx> (raw)
In-Reply-To: <1372560809.2776.159@driftwood>

On Sat, Jun 29, 2013 at 09:53:29PM -0500, Rob Landley wrote:
> On 06/29/2013 06:50:41 PM, Rich Felker wrote:
> >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.
> 
> So this would be about the "feature complte for
> not-internationalized C99" level?

It should already be feature-complete for C99, except possibly some
bugs in the time stuff I want to overhaul. There are a few things
missing for POSIX (some new strftime field width stuff comes to mind),
but not much; probably a few more small details for XSI option in the
way of interfaces that nobody uses, like encrypt(). And some things
missing for C11, of course.

> I'll try to get support into aboriginal linux for that release.

Great! Yes, this sounds like a good target version for you, especially
since I'm hoping to swat a lot more bugs by then (see the hybrid audit
item above). It should also give us plenty of time to resolve any
issues you encounter using musl with aboriginal between then and musl
1.0 so that everything is really polished when we get to 1.0.

Rich


  reply	other threads:[~2013-06-30  3:01 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-29 23:50 Rich Felker
2013-06-30  2:53 ` Rob Landley
2013-06-30  3:01   ` Rich Felker [this message]
2013-06-30  5:20 ` Isaac
2013-06-30  5:34   ` Rich Felker
2013-06-30  6:42     ` Isaac
2013-06-30  7:21       ` Justin Cormack
2013-06-30 12:02         ` Rich Felker
2013-07-04 18:13         ` Rob Landley
2013-07-07 20:25           ` Isaac
2013-07-04 18:10       ` Rob Landley
2013-07-07 20:30         ` Isaac
2013-06-30  9:24     ` Rob Landley
2013-06-30 10:45     ` Szabolcs Nagy
2013-06-30 21:29       ` Luca Barbato
2013-07-05 15:12   ` Rob Landley
2013-06-30  5:49 ` Strake
2013-07-17 16:02 ` Rich Felker
2013-07-24 18:36   ` Rob Landley
2013-07-24 19:47     ` Rich Felker
2013-07-25  7:25       ` Daniel Cegiełka
2013-07-25  7:40         ` Rich Felker
2013-07-27  5:30       ` Rob Landley
2013-07-25 10:29     ` Timo Teras
2013-07-24 14:14 ` orc
2013-07-24 14:42   ` Rich Felker
2013-07-24 15:29     ` orc
2013-07-24 16:04       ` Rich Felker
2013-07-24 16:25         ` orc
2013-07-24 19:41           ` Rich Felker

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=20130630030150.GO29800@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).