public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Andreas K. Huettel" <dilfridge@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] making the stable tree more up-to-date
Date: Mon, 21 Nov 2011 13:14:13 +0100	[thread overview]
Message-ID: <201111211314.20292.dilfridge@gentoo.org> (raw)
In-Reply-To: <4ECA0EA3.8020407@gentoo.org>

[-- Attachment #1: Type: Text/Plain, Size: 2017 bytes --]


Pawel, 

while I appreciate very much what you are doing, there is one obvious problem: usually, as a maintainer, one does not file a stablereq for a single arch, but for all stable arches of a package. 

Are the cited advances relevant for all stable arches, for the "major ones", or only for one of them?

I would like to avoid the situation that we all file stable requests like mad and end up with all-but-one swamped arch teams and a neverending list of open stabilization bugs waiting for the last arch.

Cheers, 
Andreas


Am Montag 21 November 2011, 09:41:07 schrieb Paweł Hajdan, Jr.:
> I think that with recent advancements in batch-stabilization we're able
> to process a much higher amount of stabilization bugs, and keep the bug
> queue low. It used to be longer than 100 bugs, but now it's closer to
> 20-30 bugs for which regressions or other problems have been detected.
> 
> This allows us to do better testing of the stabilization candidates, but
> also I think we should start bringing even more updates to the stable tree.
> 
> When doing stable testing I frequently notice bugs fixed in ~arch but
> not stabilized, so stable is frequently affected by problems that could
> be easily fixed by stabilizing a more recent version.
> 
> I wrote a script,
> <http://git.overlays.gentoo.org/gitweb/?p=proj/arch-tools.git;a=blob;f=stabilization-candidates.py;hb=HEAD>,
> that scans the tree for packages that could be easily stabilized (all
> deps stable, no bugs).
> 
> I'm attaching a list of packages that are sitting in the tree for at
> least 6 months (180 days, way more than 30 days required for
> stabilization) and should be ready for stabilization.
> 
> Please review the list, it's 800+ packages so I thought about asking for
> feedback before filing stabilization bugs (I plan to do that in stages
> of course).
> 
> Paweł
> 


-- 
Andreas K. Huettel
Gentoo Linux developer - kde, sci, arm, tex
dilfridge@gentoo.org
http://www.akhuettel.de/

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

  parent reply	other threads:[~2011-11-21 12:15 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 [this message]
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."
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=201111211314.20292.dilfridge@gentoo.org \
    --to=dilfridge@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