mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Natanael Copa <ncopa@alpinelinux.org>
To: Rich Felker <dalias@libc.org>
Cc: musl@lists.openwall.com
Subject: Re: musl 1.0.x branch
Date: Mon, 9 Jun 2014 11:23:52 +0200	[thread overview]
Message-ID: <20140609112352.1e7ad51e@ncopa-desktop.alpinelinux.org> (raw)
In-Reply-To: <20140606175617.GA3914@brightrain.aerifal.cx>

On Fri, 6 Jun 2014 13:56:17 -0400
Rich Felker <dalias@libc.org> wrote:

> I'm about to prepare the 1.0.3 release, and I've been thinking a bit
> about the future of the 1.0.x branch. Specifically I'd like to gauge
> the extent to which it's being used. So far cherry-picking fixes to it
> has been pretty easy, but it's an extra task to keep up with, and the
> cherry-picking is probably going to turn into active backporting
> somewhere in the near future as the rs-1.0 and master branches
> continue to diverge.
> 
> If I don't hear back that there's significant use of the 1.0.x
> releases by multiple projects, I'll probably plan to discontinue them
> in the next 4 to 6 months, and in the mean time, to release only when
> there are serious bugs (as opposed to releasing alongside every 1.1.x
> release). Does this sound reasonable?

Yes. I guess you could just drop 1.0.x support now and consider re-open
it if you get complains.
 
> If anyone's using 1.0.x not for the sake of stability but because it
> works better in some way for your setup (e.g. size, performance,
> application compatibility, etc.) please let me know about that too so
> we can see if there's a reasonable way to make 1.1.x work just as well
> for you.

Alpine Linux appreciate the idea of stable/maintenance branches, but we
figured that we'd be better off with the 1.1.x for out 3.0 stable
release. (which is kinda beta anyways). We need the new features.

So no interest in 1.0.x branch for Alpine Linux.

> 
> Rich

-nc


  parent reply	other threads:[~2014-06-09  9:23 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-06 17:56 Rich Felker
2014-06-06 19:39 ` u-igbb
2014-06-07  6:23   ` Kevin Bortis
2014-06-07 13:16 ` Anthony G. Basile
2014-06-07 18:26 ` Gustavo Zacarias
2014-06-09  9:23 ` Natanael Copa [this message]
2014-06-09 20:08   ` Rich Felker
2014-06-10  9:43     ` u-igbb
2014-06-10 16:03       ` Rich Felker
2014-06-10 16:50         ` Laurent Bercot
2014-06-10 17:37           ` Rich Felker
2014-06-10 19:19             ` Laurent Bercot
2014-06-10 21:01               ` Rich Felker
2014-06-11  1:27                 ` Laurent Bercot
2014-06-10 20:32         ` u-igbb
2014-06-10 21:51           ` Rich Felker
2014-06-11 10:24             ` u-igbb
2014-06-11 13:09               ` Rich Felker
2014-06-11 14:37                 ` u-igbb
2014-06-10 21:25         ` Natanael Copa
2014-06-10 21:13           ` musl 1.0.x branch -- OT u-igbb
2014-06-10 21:55           ` musl 1.0.x branch Rich Felker
2014-06-11 10:41 ` Oliver Schneider
2014-06-11 13:16   ` Rich Felker
2014-06-12 18:46     ` Oliver Schneider
2014-06-13  1:23       ` 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=20140609112352.1e7ad51e@ncopa-desktop.alpinelinux.org \
    --to=ncopa@alpinelinux.org \
    --cc=dalias@libc.org \
    --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).