From: "Tomáš Chvátal" <scarabeus@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [RFC] Reworking package stabilization policies
Date: Sun, 28 Mar 2010 12:04:29 +0200 [thread overview]
Message-ID: <4BAF29AD.7090505@gentoo.org> (raw)
In-Reply-To: <20100328083918.48f5835b@snowmobile>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Dne 28.3.2010 09:39, Ciaran McCreesh napsal(a):
> On Sun, 28 Mar 2010 07:47:27 +0200
> Maciej Mrozowski <reavertm@gmail.com> wrote:
>> No, seriously - given the fact that some of my packages were even
>> stabilized without contacting me (app-misc/hal-cups-utils,
>> app-admin/system-config- printer-common) - I think it should be:
>
> Well you'd marked them "~arch", right? That means they're candidates to
> go stable.
>
Yes, but last time i checked we have consensus that archies should wait
onto maintainer to request the stabling.
>> * solely up to the package maintainers to stabilize application on
>> arches they're using or on any arch if package is arch-agnostic
>> (optionally, but preferably with some peer review from other project
>> members or arch team members).
>
> There are no arch agnostic packages.
I can find some, for example kde-l10n O:P But you are right.
>
>> It's really freaking silly to wait months for stabilization of some
>> random php/perl library that's known to work.
>
> How do you know it works if you don't test on the arch in question?
>
Basically you are saying that NONE tested that package on the arch until
the stablerequest. That's quite wrong and it should mean that the arch
should be ~ only, since they are stabling packages that they first
tested the day they stable them.
Tomas
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.14 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAkuvKa0ACgkQHB6c3gNBRYdaWACdGP3EvuvL3+GVXI8GBsU3fHqj
Kq8AoJMyVDS8P0vCXfwJuGIIEQHWPgUL
=CO3D
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2010-03-28 10:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-27 20:58 [gentoo-dev] reminding slacker arch's to handle bugs William Hubbs
2010-03-28 5:47 ` [gentoo-dev] [RFC] Reworking package stabilization policies Maciej Mrozowski
2010-03-28 6:31 ` Alistair Bush
2010-03-28 6:34 ` Brian Harring
2010-03-28 6:56 ` Alistair Bush
2010-03-28 9:43 ` [gentoo-dev] " Duncan
2010-03-28 20:35 ` [gentoo-dev] " William Hubbs
2010-03-28 7:39 ` Ciaran McCreesh
2010-03-28 10:04 ` Tomáš Chvátal [this message]
2010-03-28 11:32 ` Richard Freeman
2010-03-28 15:18 ` Maciej Mrozowski
2010-03-29 7:30 ` Peter Volkov
2010-03-29 17:10 ` Maciej Mrozowski
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=4BAF29AD.7090505@gentoo.org \
--to=scarabeus@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