From: Markos Chandras <hwoarang@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Policy for late/slow stabilizations
Date: Sun, 27 Jun 2010 19:01:13 +0100 [thread overview]
Message-ID: <20100627180113.GA12949@Blade> (raw)
In-Reply-To: <20100627184330.4888ce8a@snowcone>
[-- Attachment #1: Type: text/plain, Size: 1055 bytes --]
On Sun, Jun 27, 2010 at 06:43:30PM +0100, Ciaran McCreesh wrote:
>
> 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
Please explain me why keeping foobar-1.0 ( Released in 10/12/2009 ) is
in favor of a ppc64 stable user when amd64/x86 has foobar-2.1.3 (
Released 60 days ago ) already stabled for them
What if a foobar-1.0 bug pops up? What kind of support will that user
get from the gentoo or upstream maintainer. The most frequent answer
would be "Please update to 2.1.3. 1.0 is 0ld". Yes, not droppping the
keywords is convenient for users but in this case their stable tree gets
obsolet and unsupported
--
Markos Chandras (hwoarang)
Gentoo Linux Developer
Web: http://hwoarang.silverarrow.org
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2010-06-27 18:01 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 [this message]
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=20100627180113.GA12949@Blade \
--to=hwoarang@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