public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
From: Rich Freeman <rich0@gentoo.org>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] Re: Systemd migration: opinion and questions
Date: Wed, 20 May 2015 07:22:39 -0400	[thread overview]
Message-ID: <CAGfcS_nesCHrH5qdrC+Z=-62Fs5HfpF0kxLqvjEDUb0hNUVTtg@mail.gmail.com> (raw)
In-Reply-To: <pan$e22a5$5235f4a9$3d907b34$97ad4b1c@cox.net>

On Wed, May 20, 2015 at 6:44 AM, Duncan <1i5t5.duncan@cox.net> wrote:
>
> Status: resolved/fixed, with the git commit listed/linked, less than two
> weeks after filing.  =:^) Tho of course a release with the fix hasn't yet
> been made, and a fix in under two weeks there without even a comment in
> over a month on the IPv4-only bug doesn't bode so well for the latter.

I don't think systemd has any kind of stable release strategy, and I
think that is going to become a problem.  There are a lot of cases
where there are dramatic behavior changes or big feature changes, and
they're mixed in with fixes.

So, you can't use 219 because it lacks fixes to some bugs.
Systemd-220 will probably fix those, and change who-knows-what else.

They're relying on distros to backport fixes for them, essentially.
Gentoo has been doing just that, but this just means that Gentoo's
stable version of systemd is different from Debian or Arch's, and so
on.

For such a critical piece of software they really ought to start some
fixes branches with minor releases.  They don't necessarily need to
have 5-year LTS releases (though I'm sure they'd be appreciated
considering the nature of the software), but having some minor
releases for the last major version or two certainly wouldn't hurt.

-- 
Rich


  reply	other threads:[~2015-05-20 11:22 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-24 20:15 [gentoo-amd64] Systemd migration: opinion and questions Marc Joliet
2015-02-24 20:41 ` Randy Barlow
2015-02-24 23:11   ` Marc Joliet
2015-02-25 22:42     ` Marc Joliet
2015-02-27 22:29       ` Marc Joliet
2015-02-24 21:44 ` Rich Freeman
2015-02-25  7:50   ` Marc Joliet
2015-02-25 12:01     ` Rich Freeman
2015-02-25 18:25       ` Marc Joliet
2015-03-01 12:48         ` Marc Joliet
2015-03-01 13:34           ` Rich Freeman
2015-03-01 18:20             ` Marc Joliet
2015-03-01 19:13               ` Rich Freeman
2015-03-02  5:13                 ` [gentoo-amd64] " Duncan
2015-03-14 14:01                   ` Marc Joliet
2015-03-14 12:57                 ` [gentoo-amd64] " Marc Joliet
2015-03-14 13:02               ` Marc Joliet
2015-02-25 10:13   ` [gentoo-amd64] " Duncan
2015-02-25 12:13     ` Rich Freeman
2015-02-26  0:35       ` Duncan
2015-02-25 18:56     ` Marc Joliet
2015-02-26  1:55       ` Duncan
2015-02-24 21:51 ` [gentoo-amd64] " Frank Peters
2015-02-25 14:31   ` Michael Mattes
2015-02-25 20:28   ` Marc Joliet
2015-02-25 10:15 ` [gentoo-amd64] " Duncan
2015-02-25 10:33 ` Duncan
2015-02-25 19:17   ` Marc Joliet
2015-02-25 19:31     ` Rich Freeman
2015-02-25 19:54       ` Marc Joliet
2015-02-25 22:30 ` [gentoo-amd64] " Marc Joliet
2015-05-20  8:01 ` Marc Joliet
2015-05-20 10:44   ` [gentoo-amd64] " Duncan
2015-05-20 11:22     ` Rich Freeman [this message]
2015-05-21  9:36       ` Duncan
2015-05-21 11:33         ` Marc Joliet
2015-05-23  8:49         ` Marc Joliet
2015-05-23  9:32           ` Marc Joliet
2015-05-23 10:41           ` Duncan
2015-05-23 11:11             ` Marc Joliet
2015-05-23 11:37               ` Rich Freeman
2015-05-23 12:02                 ` Duncan
2015-05-23 18:07               ` Marc Joliet
2015-05-23  8:17       ` Duncan
2015-05-23 12:14         ` Duncan
2015-05-21 11:29     ` Marc Joliet
  -- strict thread matches above, loose matches on Subject: below --
2015-02-25 11:04 Duncan

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='CAGfcS_nesCHrH5qdrC+Z=-62Fs5HfpF0kxLqvjEDUb0hNUVTtg@mail.gmail.com' \
    --to=rich0@gentoo.org \
    --cc=gentoo-amd64@lists.gentoo.org \
    /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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox