public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Christopher Head <chead@chead.ca>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] About reducing or even removing stable tree for some arches
Date: Fri, 20 Feb 2015 00:06:34 -0800	[thread overview]
Message-ID: <20150220000634.60556379@kruskal.home.chead.ca> (raw)
In-Reply-To: <54E213CA.1090602@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 1519 bytes --]

On Mon, 16 Feb 2015 10:59:06 -0500
Joshua Kinard <kumba@gentoo.org> wrote:

> Once we complete the git migration, why not take a second look on
> using a stable/testing/unstable (or -RELEASE/-STABLE/-CURRENT) system
> used by Debian and FreeBSD?  That should be entirely doable under a
> git tree versus CVS.  It would require beefing releng up again and a
> whole host of other issues.
> 
> Keep the core git tree constantly rolling forward, have a dedicated
> branch get cut say, once a year (or less -- Debian is ~18mo?),
> another group of devs works on stabilizing that (and periodically
> cherrypicking from the master branch), and when the time comes,
> totally freeze that for security revs only by a smaller group of devs?

Personally, one of the things that I love about Gentoo is that I never
have to deal with EVERYTHING changing all at once. Sure, things may
change more often through the year than they do with staged releases,
but it’s all spread out over the year, so that in any given week, what
changes is a nice, bite-sized chunk of my system, so that I can easily
isolate and deal with any problems—rather than a staged release that
upgrades 150 packages, leaving a dozen things broken and no idea where
to start looking.

Also, from a more pragmatic point of view, I don’t particularly want to
have to *compile* a year’s worth of new packages at one moment in
time—better to spend an hour here, an hour there, spread out over the
weeks.
-- 
Christopher Head

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 648 bytes --]

  parent reply	other threads:[~2015-02-20 23:25 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-16 13:34 [gentoo-dev] About reducing or even removing stable tree for some arches Pacho Ramos
2015-02-16 15:09 ` Rich Freeman
2015-02-16 15:16   ` Pacho Ramos
2015-02-16 15:36 ` Anthony G. Basile
2015-02-16 15:59   ` Joshua Kinard
2015-02-16 23:28     ` Rich Freeman
2015-02-20  8:06     ` Christopher Head [this message]
2015-02-16 16:05   ` Pacho Ramos
2015-02-16 21:22     ` Anthony G. Basile
2015-02-16 22:45       ` Mike Gilbert
2015-02-16 16:37 ` William Hubbs
2015-02-17  4:49   ` Michał Górny
2015-02-16 22:47 ` William Hubbs
2015-02-18  3:11 ` [gentoo-dev] " Duncan
2015-02-18  9:25   ` Pacho Ramos

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=20150220000634.60556379@kruskal.home.chead.ca \
    --to=chead@chead.ca \
    --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