public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Tony \"Chainsaw\" Vroon" <chainsaw@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Policy for late/slow stabilizations
Date: Sun, 27 Jun 2010 19:37:39 +0100	[thread overview]
Message-ID: <1277663859.12853.4.camel@localhost> (raw)
In-Reply-To: <20100627150445.GA19456@Eternity>

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

On Sun, 2010-06-27 at 18:04 +0300, Markos Chandras wrote:
> As many of you have already noticed, there are some arches that are quite
> slow on stabilizations. This leads to deprecated stabilizations e.g a
> package is stabilized after 60 days which makes that version of
> the specific package obsolete and not worth to stabilize anymore.

So you would suggest to be like Ubuntu and say "we can not be bothered
to support any minority architectures anymore". This effectively
disbands all architecture teams except AMD64 and X86; it should be
subject to the same scrutiny (I suggest a council vote) as a GLEP or
EAPI change.
Personally I would like to hear stronger reasons then "it inconveniences
me when a bug I file is open longer then a month" to destroy the current
diversity of supported architectures (be it PowerPC or a prefix
installation on OS X).

Regards,
Tony V.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  parent reply	other threads:[~2010-06-27 18:37 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
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 [this message]
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=1277663859.12853.4.camel@localhost \
    --to=chainsaw@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