From: Ciaran McCreesh <ciaran.mccreesh@googlemail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Proposal for how to handle stable ebuilds
Date: Mon, 10 Nov 2008 18:23:19 +0000 [thread overview]
Message-ID: <20081110182319.032930f2@snowcone> (raw)
In-Reply-To: <20081110181334.GD7038@aerie.halcy0n.com>
[-- Attachment #1: Type: text/plain, Size: 1075 bytes --]
On Mon, 10 Nov 2008 13:13:34 -0500
Mark Loeser <halcy0n@gentoo.org> wrote:
> Arch teams will normally have 30 days from the day a bug was filed,
> keyworded STABLEREQ, the arch was CCed, and the maintainer either
> filed the bug or commented that it was OK to stabilize (clock starts
> when all of these conditions are met).
30 days is a minimum, not a maximum.
> If an ebuild meets the time criteria above, and there are no
> technical issues preventing stabilization, then the maintainer MAY
> choose to delete an older version even if it is the most recent
> stable version for a particular arch.
All this does is screw over users. The impact of a forced downgrade is
far higher than the impact of leaving things in the tree for as long as
is necessary.
You are proposing giving maintainers carte blanche to screw over users
and encouraging rather than reducing the kind of "us vs them" behaviour
that a few package maintainers like to engage in where arch teams are
treated as being in the way rather than there to help.
--
Ciaran McCreesh
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2008-11-10 18:23 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-10 18:13 [gentoo-dev] Proposal for how to handle stable ebuilds Mark Loeser
2008-11-10 18:23 ` Ciaran McCreesh [this message]
2008-11-10 18:23 ` Mart Raudsepp
2008-11-10 20:32 ` Steev Klimaszewski
2008-11-10 21:16 ` Jeremy Olexa
2008-11-10 21:57 ` Santiago M. Mola
2008-11-11 0:24 ` Jose Luis Rivero
2008-11-11 1:13 ` Mark Loeser
2008-11-11 9:31 ` Jose Luis Rivero
2008-11-11 1:21 ` Richard Freeman
2008-11-11 8:56 ` Peter Volkov
2008-11-11 10:18 ` Jose Luis Rivero
2008-11-11 13:49 ` Ferris McCormick
2008-11-11 16:06 ` [gentoo-dev] " Duncan
2008-11-11 16:24 ` Jeroen Roovers
2008-11-11 17:26 ` Duncan
2008-11-11 17:55 ` Ferris McCormick
2008-11-11 18:12 ` Jeroen Roovers
2008-11-11 21:03 ` Duncan
2008-11-13 17:38 ` [gentoo-dev] " Tobias Scherbaum
2008-11-15 13:02 ` Matti Bickel
2008-11-17 18:08 ` Tobias Scherbaum
2008-11-17 19:03 ` [gentoo-dev] " Duncan
2008-12-11 5:35 ` [gentoo-dev] " Donnie Berkholz
2008-11-17 0:38 ` [gentoo-dev] " Ryan Hill
2008-11-17 15:10 ` Daniel Gryniewicz
2008-11-18 1:08 ` Ryan Hill
2008-11-18 16:57 ` Daniel Gryniewicz
2008-11-18 17:50 ` Ciaran McCreesh
2008-11-18 20:31 ` Daniel Gryniewicz
2008-11-18 21:18 ` Ryan Hill
2008-11-18 22:04 ` Daniel Gryniewicz
2008-11-18 22:45 ` Ryan Hill
2008-11-30 22:59 ` Ryan Hill
2008-12-01 7:49 ` Peter Volkov
2008-12-11 5:37 ` [gentoo-dev] " Donnie Berkholz
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=20081110182319.032930f2@snowcone \
--to=ciaran.mccreesh@googlemail.com \
--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