public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Markos Chandras <hwoarang@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Policy for late/slow stabilizations
Date: Sun, 27 Jun 2010 18:54:36 +0300	[thread overview]
Message-ID: <20100627155436.GA19598@Eternity> (raw)
In-Reply-To: <1277653669.22988.3.camel@TesterBox.tester.ca>

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

On Sun, Jun 27, 2010 at 11:47:49AM -0400, Olivier Crête wrote:
> On Sun, 2010-06-27 at 18:04 +0300, Markos Chandras wrote:
> > Moreover, slow arches introduce another problem as well. If a package is
> > marked stabled for their arch, but this package is quite old, and they fail to
> > stabilize a new version, we ( as maintainers ) can't drop the very old
> > ( and obsolete ) version of this package because we somehow will break
> > the stable tree for these arches. How should we act in this case?
> > Keep the old version around forever just to say that "hey, they do have
> > a stable version for our exotic arch".
> 
> I'd propose waiting a bit longer than 30 days.. Maybe 90 days, and then
> just drop the old ebuild. These arches will slowly lose stable keywords
> until their stable tree gets to a size that they can manage. And
> everyone will be winners. That said, when dropping the old keywords, you
> have to be careful to drop the stable keyword on all dependencies too so
> as to not drop break the tree for them.
>
When dropping an old *stable* ebuild, which in most cases this will be the
only stable ebuild that these arches will have for this packages, the
next world update will be ugly since there will be no *stable *
candidates for that package anymore. In this case, stable users will
start filling package.keywords leading to ~testing migration. So I am
not sure if this is the correct approach to deal with this but I can't
think of anything else
> -- 
> Olivier Crête
> tester@gentoo.org
> Gentoo Developer



-- 
Markos Chandras (hwoarang)
Gentoo Linux Developer
Web: http://hwoarang.silverarrow.org

[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2010-06-27 15:56 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-27 15:04 [gentoo-dev] Policy for late/slow stabilizations Markos Chandras
2010-06-27 15:45 ` Patrick Lauer
2010-06-27 18:40   ` Tony "Chainsaw" Vroon
2010-06-27 15:47 ` Olivier Crête
2010-06-27 15:54   ` Markos Chandras [this message]
2010-06-27 18:21     ` Olivier Crête
2010-06-27 20:00       ` Markos Chandras
2010-06-27 16:30   ` Samuli Suominen
2010-06-28  3:53   ` Jeroen Roovers
2010-06-27 16:38 ` Ciaran McCreesh
2010-06-27 17:22   ` Markos Chandras
2010-06-27 17:43     ` Ciaran McCreesh
2010-06-27 18:01       ` Markos Chandras
2010-06-27 18:13         ` Ciaran McCreesh
2010-06-28  9:21       ` [gentoo-dev] " Duncan
2010-06-27 16:53 ` [gentoo-dev] " Auke Booij
2010-06-27 17:16   ` Markos Chandras
2010-06-27 18:15     ` Auke Booij
2010-06-27 19:58       ` Markos Chandras
2010-06-28  7:49         ` Thilo Bangert
2010-06-28 12:01           ` Mart Raudsepp
2010-06-27 18:07 ` Arfrever Frehtes Taifersar Arahesis
2010-06-27 18:37 ` Tony "Chainsaw" Vroon
2010-06-27 19:55   ` Markos Chandras
2010-06-27 20:01     ` Ciaran McCreesh
2010-06-27 20:10       ` Markos Chandras
2010-06-27 20:29 ` Nirbheek Chauhan
2010-06-27 21:38   ` Markos Chandras
2010-06-27 23:08     ` Nirbheek Chauhan

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=20100627155436.GA19598@Eternity \
    --to=hwoarang@gentoo.org \
    --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