public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Pacho Ramos <pacho@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: making the stable tree more up-to-date
Date: Thu, 24 Nov 2011 18:26:11 +0100	[thread overview]
Message-ID: <1322155571.6162.1.camel@belkin4> (raw)
In-Reply-To: <CAGfcS_nWJ7LRYTzexE2E++JqEECw2pOrgYEipB2VSiw+hffD2A@mail.gmail.com>

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

El jue, 24-11-2011 a las 12:12 -0500, Rich Freeman escribió:
> On Thu, Nov 24, 2011 at 11:35 AM, Ian Stakenvicius <axs@gentoo.org> wrote:
> > .should ~arch packages with no maintainer really be moved to stable?*
> >
> > (* assuming no other outside forces, like it's a dep of something else
> > that needs to go stable)
> 
> I support stabilizing bug-free newer versions of maintainer-needed
> packages that already have stable versions.  I'm not sure I'd extend
> that to stabilizing packages that have no stable versions already.
> 

I agree with stabling newer version but NOT to stable maintainer-needed
packages that has no stable version currently :)

> I see getting stable users on the ~arch version as a win-win since it
> means less maintenance of older version (without a maintainer), and
> will likely give the stable user a more stable experience in reality
> than what they already have.
> 

I have also seen some maintainer-needed packages need to get a newer
version stable to fix some old opened bugs 

> Those benefits don't exist for a package that has no stable versions
> to begin with.
> 
> Rich
> 
> 



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

  reply	other threads:[~2011-11-24 17:26 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-21  8:41 [gentoo-dev] making the stable tree more up-to-date "Paweł Hajdan, Jr."
2011-11-21 11:48 ` Ulrich Mueller
2011-11-21 12:14 ` Andreas K. Huettel
2011-11-21 12:24   ` "Paweł Hajdan, Jr."
2011-11-21 12:27   ` Rich Freeman
2011-11-21 13:12 ` James Broadhead
2011-11-21 15:47 ` Brian Dolbec
2011-11-23 14:27 ` [gentoo-dev] " Torsten Veller
2011-11-24 15:17   ` "Paweł Hajdan, Jr."
2011-11-24 16:35     ` Ian Stakenvicius
2011-11-24 17:12       ` Rich Freeman
2011-11-24 17:26         ` Pacho Ramos [this message]
2011-11-29 12:18         ` "Paweł Hajdan, Jr."
2011-11-25 16:39 ` [gentoo-dev] " Thomas Kahle
2011-11-25 19:06   ` Mr. Aaron W. Swenson
2011-11-29 12:17   ` "Paweł Hajdan, Jr."
2011-12-16 10:42 ` justin
2011-12-16 11:06   ` Agostino Sarubbo
2011-12-16 11:10     ` Anthony G. Basile
2011-12-16 11:21       ` Agostino Sarubbo
2011-12-16 11:46         ` justin
2011-12-18 10:59           ` [gentoo-dev] checking C*FLAGS used for build (was: making the stable tree more up-to-date) Michał Górny
2011-12-16 11:07   ` [gentoo-dev] making the stable tree more up-to-date Brian Harring
2011-12-16 13:27   ` "Paweł Hajdan, Jr."
2011-12-16 13:53     ` Rich Freeman
2011-12-16 14:05       ` Andreas K. Huettel
2011-12-16 18:40         ` Tim Harder
2011-12-16 14:12     ` justin
2011-12-17 15:25       ` "Paweł Hajdan, Jr."

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=1322155571.6162.1.camel@belkin4 \
    --to=pacho@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