mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Isaac <idunham@lavabit.com>
To: musl@lists.openwall.com
Subject: Re: Proposed roadmap to 1.0
Date: Sat, 29 Jun 2013 22:20:45 -0700	[thread overview]
Message-ID: <20130630052045.GB1368@newbook> (raw)
In-Reply-To: <20130629235041.GA5046@brightrain.aerifal.cx>

On Sat, Jun 29, 2013 at 07:50:41PM -0400, Rich Felker wrote:
> Hi all,
> 
> Here is a VERY tentative, proposed roadmap towards a 1.0 release of
> musl. Comments welcome!
> 
> 0.9.11
> Projected release: ASAP
> No further goals at the moment except fixing additional bugs found.

+1
 
> 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.

How about s390 and ia64? ;-)

All joking aside, I'd say +1. 
And for ports, arm64, mips64 or mips n32, x32, and/or sh seem like
interesting targets. 
While sparc is not "dead", basically leon is the only sparc cpu that is 
alive and likely to provide an interested audience.
And that's sparc32.
m68k/coldfire are 32-bit only, slow, and largely obsolete with little 
prospect of new development (Freescale is working on ppc and arm systems),
but there is some use of them in the embedded market, so I could imagine a
port being useful to someone.
Do we currently support 64-bit ppc?

ia64 appears to be limited in use/dying, besides not being the ideal target.
(big iron, and you'd pretty much need to interest Oracle and similar companies
before you get much use).
hppa and alpha are most interesting for a computer historian.
m32r is live, but I'm not aware of much interest.
tilera and epiphany (the Parallela coprocessor) sound interesting,
but are likely to be limited in availability.

Isaac Dunham



  parent reply	other threads:[~2013-06-30  5:20 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
2013-06-30  5:20 ` Isaac [this message]
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=20130630052045.GB1368@newbook \
    --to=idunham@lavabit.com \
    --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).