public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mart Raudsepp <leio@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [RFC] Improve policy of stabilizations
Date: Sun, 01 Nov 2009 18:55:29 +0200	[thread overview]
Message-ID: <1257094529.29790.2.camel@localhost> (raw)
In-Reply-To: <200911011736.38401.Arfrever@gentoo.org>

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

On Sun, 2009-11-01 at 17:36 +0100, Arfrever Frehtes Taifersar Arahesis
wrote:
> Some packages have new releases more than once a month and sometimes it's reasonable
> to not skip stabilization of any version. Given version of a package is usually no
> longer tested by users after release of a newer version, so I suggest the following
> change to the policy of stabilizations:
> Stabilization of given version of a package can be requested if this version has been
> in the tree for at least 10 days and a newer version of this package has been added
> to the tree.

I am not aware of there being a 30 day policy, and have always
considered it as a guideline, not policy. If the maintainer sees that 10
days is good for the package sometimes, I see no problem with it. Arch
teams might kindly request explanations of why the quicker
stabilization, but I don't represent any myself, but in case of quicker
stabilization of package I maintain myself I try to state in the
STABLEREQ bug why the quicker stabilization.

Is it stated in any documentation that 30 days is a policy?

-- 
Mart Raudsepp
Gentoo Developer
Mail: leio@gentoo.org
Weblog: http://planet.gentoo.org/developers/leio

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

  reply	other threads:[~2009-11-01 16:55 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-01 16:36 [gentoo-dev] [RFC] Improve policy of stabilizations Arfrever Frehtes Taifersar Arahesis
2009-11-01 16:55 ` Mart Raudsepp [this message]
2009-11-01 18:19   ` Richard Freeman
2009-11-01 20:21     ` Petteri Räty
2009-11-01 21:16 ` [gentoo-dev] " Ryan Hill
2009-11-02 14:17 ` Christian Faulhammer
2009-11-02 15:23   ` Markos Chandras
2009-11-03 18:10     ` Christian Faulhammer
2009-11-04 12:36       ` Ben de Groot
2009-11-04 12:50         ` Christian Faulhammer
2009-11-04 18:01           ` Tobias Klausmann
2009-11-04 20:49             ` Nirbheek Chauhan
2009-11-04 21:02         ` Joseph Jezak
2009-11-05  3:48           ` Ryan Hill
2009-11-05  9:17             ` Tobias Klausmann
2009-11-05 20:12               ` Petteri Räty
2009-11-06  3:06                 ` Joseph Jezak
2009-11-06 14:18                 ` Nirbheek Chauhan
2009-11-06 14:45                   ` Fabian Groffen
2009-11-06 17:06                     ` Nirbheek Chauhan
2009-11-06 17:08                       ` Nirbheek Chauhan
2009-11-07  5:13                       ` Ryan Hill
2009-11-06 22:07                     ` Zac Medico
2009-11-07  3:36                       ` Arfrever Frehtes Taifersar Arahesis
2009-11-07 14:54                       ` Peter Volkov
2009-11-07 20:49                         ` Zac Medico
2009-11-08  0:12                           ` Nirbheek Chauhan
2009-11-08  9:31                             ` Petteri Räty
2009-11-08 12:55                           ` Peter Volkov
2009-11-09  2:34                             ` Zac Medico
2009-11-08  9:05                         ` Fabian Groffen
2009-11-08 12:53                           ` Peter Volkov
2009-11-06 22:52                     ` Rémi Cardona
2009-11-07  7:22                       ` Hans de Graaff
2009-11-06 16:00                   ` Kent Fredric
2009-11-06 17:00                     ` Nirbheek Chauhan
2009-11-07 14:14                 ` Tobias Klausmann
2009-11-05 10:52             ` Duncan
2009-11-06 17:18             ` Christian Faulhammer
2009-11-06 17:15           ` Christian Faulhammer

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=1257094529.29790.2.camel@localhost \
    --to=leio@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