From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: rfc: revisiting our stabilization policy
Date: Sun, 26 Jan 2014 22:56:24 +0000 (UTC) [thread overview]
Message-ID: <pan$d1bf2$395b550e$221c2d1c$70695970@cox.net> (raw)
In-Reply-To: CAGfcS_k=aS06b7s2_Y4_TrG6ngDafeW6axWEmb4o_iTCQaSUaQ@mail.gmail.com
Rich Freeman posted on Sat, 25 Jan 2014 19:59:19 -0500 as excerpted:
> On Fri, Jan 24, 2014 at 11:02 PM, Duncan <1i5t5.duncan@cox.net> wrote:
>> I've often wondered just how much faster gentoo could move, and how
>> much better we could keep up with upstream, if we weren't so focused on
>> 30+day outdated stab?le bumping all the time. All that effort... from
>> my viewpoint going to waste on something that gentoo really isn't going
>> to be that great at anyway, certainly in comparison to other distros
>> which REALLY provide a stab?le service, up to a /decade/ outdated,
>> supporting often trailing edge software, in an effort to slow down
>> progress for people that don't want to move so fast.
>
> I get what you're saying, and I'm going to use a bit of hyperbole so
> don't take this too seriously, but couldn't you just as easily argue
> that Gentoo could go much faster if we actually took advantage of the
> fact that we DO have a stable tree, and stop being so careful about not
> breaking the testing tree?
If that was hyperbole it was a bit too subtle for me. =:^)
Actually, I'd support something like this too. After all, I've already
stated that on some packages I run from the project overlay and/or the
live-vcs version. In a way, that's arguably what testing should /be/,
tho it'd certainly be a departure from how gentoo handles things now.
Basically in my ideal gentoo, what's now stable would disappear entirely,
and what's now testing would be the new stable, with what's now hard-
masked and/or only available in the overlays being testing.
But obviously I recognize that's totally broken for a lot of people who
do depend on gentoo stable, and as such, I don't really consider it an
entirely practical option... But it'd be nice for me anyway! =:^)
So it's far from hyperbole in my world. In my world it's the ideal. =:^)
> Honestly, I think both trees represent a pretty decent balance. It is
> pretty safe to run ~arch for the packages you really are interested in,
> and run stable for the stuff that you don't care so much about, thus
> limiting your exposure to problems while getting cutting-edge where you
> care for it.
Except, well, ~arch is if anything safe enough to be stable, and
unfortunately, isn't always that cutting edge after all. One has to run
overlays and hard-unmask live-vcs versions to actually get cutting edge
testing, which is in my view... unfortunate.
> Most of the concern in this thread has been about some minor archs that
> struggle to keep up. It seems like the simplest solution in these cases
> is to just have them focus on @system packages for the stable tree, and
> let users deal with more breakage outside of that set (where it isn't
> super-disruptive). If you're running a minor arch chances are that
> you're happy to have any support at all, since you sure aren't going to
> be running Ubuntu...
Agreed.
Tho AFAIK both Ubuntu and Fedora have an arm variants... But also AFAIK,
due to them being binary distros these variants are closer to the sub-arm-
keyword-variants I believe someone else proposed in this thread (??) for
gentoo/arm as well, consequently leaving other sub-arch-variants that
gentoo/arm supports out in the cold.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next prev parent reply other threads:[~2014-01-26 22:57 UTC|newest]
Thread overview: 135+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-14 21:37 [gentoo-dev] rfc: revisiting our stabilization policy William Hubbs
2014-01-14 21:57 ` Michael Orlitzky
2014-01-14 22:33 ` William Hubbs
2014-01-14 22:43 ` Michael Orlitzky
2014-01-14 23:11 ` William Hubbs
2014-01-14 23:22 ` Jeff Horelick
2014-01-15 0:28 ` Tom Wijsman
2014-01-15 23:59 ` [gentoo-dev] " Duncan
2014-01-16 0:23 ` Tom Wijsman
2014-01-15 0:47 ` [gentoo-dev] " Michael Orlitzky
2014-01-15 1:08 ` Tom Wijsman
2014-01-15 1:11 ` Michael Orlitzky
2014-01-15 1:23 ` Tom Wijsman
2014-01-15 1:36 ` Michael Orlitzky
2014-01-15 2:09 ` William Hubbs
2014-01-15 2:21 ` Michael Orlitzky
2014-01-15 2:34 ` Tom Wijsman
2014-01-15 2:40 ` Michael Orlitzky
2014-01-15 3:26 ` Tom Wijsman
2014-01-15 2:46 ` William Hubbs
2014-01-16 7:28 ` Christopher Head
2014-01-16 22:44 ` Tom Wijsman
2014-01-19 22:31 ` Christopher Head
2014-01-20 0:47 ` Tom Wijsman
2014-01-23 18:12 ` [gentoo-dev] " Steven J. Long
2014-01-23 19:13 ` Tom Wijsman
2014-01-23 20:55 ` Steev Klimaszewski
2014-01-23 22:38 ` Tom Wijsman
2014-01-23 22:42 ` Peter Stuge
2014-01-23 23:50 ` Tom Wijsman
2014-01-24 0:04 ` Steev Klimaszewski
2014-01-24 3:04 ` Tom Wijsman
2014-01-24 3:52 ` Steev Klimaszewski
2014-01-24 17:26 ` Tom Wijsman
2014-01-24 18:10 ` Steev Klimaszewski
2014-01-24 19:29 ` Tom Wijsman
2014-01-24 20:29 ` Steev Klimaszewski
2014-01-24 21:55 ` Tom Wijsman
2014-01-24 10:46 ` Steven J. Long
2014-01-24 18:26 ` Tom Wijsman
2014-01-25 4:02 ` Duncan
2014-01-26 0:50 ` Peter Stuge
2014-01-26 0:59 ` Rich Freeman
2014-01-26 4:53 ` Peter Stuge
2014-01-26 11:41 ` Rich Freeman
2014-01-26 18:56 ` Peter Stuge
2014-01-26 21:35 ` Rich Freeman
2014-01-27 7:41 ` Steev Klimaszewski
2014-01-27 14:52 ` Rich Freeman
2014-01-28 2:45 ` Steev Klimaszewski
2014-01-26 22:56 ` Duncan [this message]
2014-01-26 23:40 ` Duncan
2014-01-28 12:37 ` Steven J. Long
2014-01-28 12:52 ` Alan McKinnon
2014-01-28 13:18 ` Tom Wijsman
2014-01-28 13:11 ` Tom Wijsman
2014-01-29 3:15 ` Duncan
2014-01-29 6:34 ` Steev Klimaszewski
2014-01-15 2:42 ` [gentoo-dev] " Tom Wijsman
2014-01-15 11:33 ` Sergey Popov
2014-01-15 16:57 ` Tom Wijsman
2014-01-15 17:20 ` Matthew Thode
2014-01-15 2:26 ` Tom Wijsman
2014-01-15 11:28 ` Sergey Popov
2014-01-15 0:13 ` Tom Wijsman
2014-01-15 0:50 ` Michael Orlitzky
2014-01-15 1:13 ` Tom Wijsman
2014-01-15 23:13 ` [gentoo-dev] " Duncan
2014-01-15 0:04 ` [gentoo-dev] " Tom Wijsman
2014-01-14 23:49 ` Tom Wijsman
2014-01-15 0:06 ` Andreas K. Huettel
2014-01-15 0:17 ` Anthony G. Basile
2014-01-15 0:43 ` Tom Wijsman
2014-01-15 0:38 ` Tom Wijsman
2014-01-15 0:46 ` William Hubbs
2014-01-15 1:26 ` Tom Wijsman
2014-01-15 11:40 ` Sergey Popov
2014-01-15 17:04 ` Tom Wijsman
2014-01-16 6:20 ` Sergey Popov
2014-01-16 15:54 ` Peter Stuge
2014-01-16 17:56 ` Rich Freeman
2014-01-16 18:04 ` Alan McKinnon
2014-01-16 18:26 ` Peter Stuge
2014-01-16 20:18 ` Alan McKinnon
2014-01-16 20:40 ` Peter Stuge
2014-01-16 18:11 ` Peter Stuge
2014-01-16 18:42 ` Rich Freeman
2014-01-16 19:29 ` William Hubbs
2014-01-16 19:59 ` Peter Stuge
2014-01-16 22:49 ` Tom Wijsman
2014-01-15 3:48 ` grozin
2014-01-15 4:49 ` William Hubbs
2014-01-15 5:07 ` Robin H. Johnson
2014-01-15 8:03 ` Dirkjan Ochtman
2014-01-15 8:18 ` Hans de Graaff
2014-01-15 16:11 ` [gentoo-dev] " Michael Palimaka
2014-01-15 9:54 ` [gentoo-dev] " Michał Górny
2014-01-15 12:51 ` Rich Freeman
2014-01-15 21:41 ` [gentoo-dev] " Duncan
2014-01-15 11:24 ` [gentoo-dev] " Sergey Popov
2014-01-15 11:30 ` Sergey Popov
2014-01-15 15:30 ` William Hubbs
2014-01-16 6:17 ` Sergey Popov
2014-01-17 6:06 ` grozin
2014-01-17 7:02 ` grozin
2014-01-17 7:58 ` Matt Turner
2014-01-17 15:02 ` Rich Freeman
2014-01-17 15:02 ` Michał Górny
2014-01-18 1:35 ` William Hubbs
2014-01-17 15:31 ` Ulrich Mueller
2014-01-17 16:47 ` Tom Wijsman
2014-01-17 17:08 ` grozin
2014-01-18 0:34 ` Manuel Rüger
2014-01-17 18:28 ` Ciaran McCreesh
2014-01-17 23:56 ` Tom Wijsman
2014-01-18 12:59 ` [gentoo-dev] arch="any" (Re: rfc: revisiting our stabilization policy) Steven J. Long
2014-01-17 17:07 ` noarch packages, was Re: [gentoo-dev] rfc: revisiting our stabilization policy grozin
2014-01-19 8:36 ` Mike Frysinger
2014-01-19 9:28 ` Add a KEYWORD representing any arch (was: Re: [gentoo-dev] rfc: revisiting our stabilization policy) Pacho Ramos
2014-01-19 9:46 ` [gentoo-dev] Re: Add a KEYWORD representing any arch Ulrich Mueller
2014-01-19 10:15 ` Pacho Ramos
2014-01-20 19:25 ` Steev Klimaszewski
2014-01-22 15:46 ` Jeroen Roovers
2014-01-19 9:48 ` Add a KEYWORD representing any arch (was: Re: [gentoo-dev] rfc: revisiting our stabilization policy) Mike Frysinger
2014-01-17 21:04 ` [gentoo-dev] rfc: revisiting our stabilization policy Maciej Mrozowski
2014-01-15 18:33 ` Thomas Sachau
2014-01-15 19:07 ` William Hubbs
2014-01-16 0:58 ` Steev Klimaszewski
2014-01-16 2:32 ` Robin H. Johnson
2014-01-16 5:47 ` Steev Klimaszewski
2014-01-19 11:06 ` Thomas Sachau
2014-01-16 6:27 ` Sergey Popov
2014-01-16 7:15 ` [gentoo-dev] " Michael Palimaka
2014-01-15 19:13 ` [gentoo-dev] " Ruud Koolen
2014-01-15 21:54 ` [gentoo-dev] " Martin Vaeth
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='pan$d1bf2$395b550e$221c2d1c$70695970@cox.net' \
--to=1i5t5.duncan@cox.net \
--cc=gentoo-dev@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