public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ciaran McCreesh <ciaran.mccreesh@googlemail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Policy for late/slow stabilizations
Date: Sun, 27 Jun 2010 18:43:30 +0100	[thread overview]
Message-ID: <20100627184330.4888ce8a@snowcone> (raw)
In-Reply-To: <20100627172233.GB1414@Mystical>

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

On Sun, 27 Jun 2010 20:22:33 +0300
Markos Chandras <hwoarang@gentoo.org> wrote:
> > Which does Gentoo care about more: slightly increased convenience
> > for most developers, or considerably increased inconvenience for
> > users of minority archs?
> > 
> I don't follow you. Increased convenience just for the devs? How?

Not having to keep old versions around for a few archs is slightly more
convenient for most people.

Having to deal with dropped keywords is a huge inconvenience for users
on minority archs.

> All I want is to have packages stabled ~60 days after the initial
> commit on tree instead of ~5 months. If arches can't do that then I
> don't want to mark that obsolete package stable at all. Whats the
> point?

The point is for users of minor archs to have something that works.

> Also I would prefer to be able to drop ancient stable packages
> from the tree even if that means that there wont be any other stable
> version for this package to use. I 'd prefer a working tiny stable
> tree than a huge ancient one

The problem with that is that presumably some minority arch users are
using the packages you'd be dropping. When that happens, dropped
keywords are a considerable cost to them.

Which is the decision to make: make things very difficult for minority
arch users, who get screwed over royally every time keywords are
dropped, or make things slightly more inconvenient for developers, who
have to keep some things around for longer. It's all down to whether
you think happy users are more important than happy developers.

-- 
Ciaran McCreesh

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

  reply	other threads:[~2010-06-27 17:43 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 [this message]
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=20100627184330.4888ce8a@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