public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "\"Paweł Hajdan, Jr.\"" <phajdan.jr@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] making the stable tree more up-to-date
Date: Tue, 29 Nov 2011 13:17:05 +0100	[thread overview]
Message-ID: <4ED4CD41.10402@gentoo.org> (raw)
In-Reply-To: <20111125163932.GH28718@schlaumatte.guest.mfo.de>

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

On 11/25/11 5:39 PM, Thomas Kahle wrote:
> I still remember that arfrever had such a script running for python 
> packages and that we were quite annoyed by the automatic stable bugs 
> for every minor version of every small python package.

I also still remember it, and that was one of the things that made me
start the batch-stabilization workflow.

I don't want to repeat frustration caused by that python script. If
anyone's annoyed by my script or wants to opt out, please let me know.

> For this reason I'm against running the script constantly.  Packages 
> with high release frequence upstream don't need every of their 
> versions to be stabilized.

If a package has been in the tree for 180 days, I guess we're safe. I'm
going to only consider the last ~arch package as stabilization
candidate, as requested by various maintainers.

> Personally, I think they don't even need every of their versions 
> bumped...

IMHO nothing wrong with it, and it can even be a good thing if given
team has manpower to keep up. Of course it's way more important to fix
bugs in existing packages than to bump every minor version.

> On the other hand, having a big stable frenzy once every few months 
> seems good for exactly the reasons you name.

Good, I think I still need to figure out the best way to run my script.
I'm leaning towards a more continuous fashion instead of a huge frenzy
from time to time. Each run can be limited (in fact I've limited the
last one to just 100 bugs), and in fact for my next run I'm seriously
considering filing _less_ bugs.

Partially because Agostino (ago) reported lots of problems with existing
stabilization candidates, and I think it's worth to fix them before next
round of stabilizations. :)


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 203 bytes --]

  parent reply	other threads:[~2011-11-29 12:18 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
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." [this message]
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=4ED4CD41.10402@gentoo.org \
    --to=phajdan.jr@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