From: James Broadhead <jamesbroadhead@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] making the stable tree more up-to-date
Date: Mon, 21 Nov 2011 13:12:49 +0000 [thread overview]
Message-ID: <CA+hid6GCd=2stFMaHXd=QGeXNSVB4pyObhj_NoPnf+5Bw5u6Rw@mail.gmail.com> (raw)
In-Reply-To: <4ECA0EA3.8020407@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 984 bytes --]
On 21 November 2011 08:41, "Paweł Hajdan, Jr." <phajdan.jr@gentoo.org>wrote:
>
>
> 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).
This is an excellent idea, and is exactly the kind of thing that we* need
to be doing to start keeping up with faster release cycles, and managing to
stay on top of all of the packages that are in the tree without huge
amounts of developer interaction.
Well done.
J
*IAmNotADev
[-- Attachment #2: Type: text/html, Size: 1479 bytes --]
next prev parent reply other threads:[~2011-11-21 13:14 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 [this message]
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='CA+hid6GCd=2stFMaHXd=QGeXNSVB4pyObhj_NoPnf+5Bw5u6Rw@mail.gmail.com' \
--to=jamesbroadhead@gmail.com \
--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