From: Joshua Kinard <kumba@gentoo.org>
To: gentoo-mips@lists.gentoo.org
Subject: Re: [gentoo-mips] Restore stable keywords on @system
Date: Sun, 09 Feb 2014 02:48:23 -0500 [thread overview]
Message-ID: <52F732C7.1010704@gentoo.org> (raw)
In-Reply-To: <52E18027.7050401@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1278 bytes --]
On 01/23/2014 3:48 PM, Markos Chandras wrote:
>> I think that you're probably right about the added problems of
>> attempting to keep a stable @system. Other stable architecture teams
>> aren't really able to keep up and I'm not convinced that we should
>> try.
>
> Given the limited manpower and hardware we have, I would say it is very
> hard to dedicate a box for testing a stable @system. If someone wants to
> take over this role, then fine by me, but we need to make sure he will
> be around and do this for as long as it takes.
>
> Personally, I am happy the way things are at the moment and fixing
> ~arch should be our priority
Aye, sticking with ~arch is still the best right now. Perhaps soon, we can
look at @system going stable once ~arch is nailed down. It's a bit of a
slippery slope when you go stable, because the number of packages that users
want to see stabilized usually goes up, not down. Especially once you start
supporting *anything* under X11.
--
Joshua Kinard
Gentoo/MIPS
kumba@gentoo.org
4096R/D25D95E3 2011-03-28
"The past tempts us, the present confuses us, the future frightens us. And
our lives slip away, moment by moment, lost in that vast, terrible in-between."
--Emperor Turhan, Centauri Republic
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 834 bytes --]
prev parent reply other threads:[~2014-02-09 7:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-22 20:42 [gentoo-mips] Restore stable keywords on @system Markos Chandras
2014-01-22 21:01 ` Matt Turner
2014-01-23 20:48 ` Markos Chandras
2014-02-09 7:48 ` Joshua Kinard [this message]
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=52F732C7.1010704@gentoo.org \
--to=kumba@gentoo.org \
--cc=gentoo-mips@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