| 1 |
On 21 November 2011 08:41, "Paweł Hajdan, Jr." <phajdan.jr@g.o>wrote: |
| 2 |
> |
| 3 |
> |
| 4 |
> I wrote a script, |
| 5 |
> < |
| 6 |
> http://git.overlays.gentoo.org/gitweb/?p=proj/arch-tools.git;a=blob;f=stabilization-candidates.py;hb=HEAD |
| 7 |
> >, |
| 8 |
> that scans the tree for packages that could be easily stabilized (all |
| 9 |
> deps stable, no bugs). |
| 10 |
> |
| 11 |
> I'm attaching a list of packages that are sitting in the tree for at |
| 12 |
> least 6 months (180 days, way more than 30 days required for |
| 13 |
> stabilization) and should be ready for stabilization. |
| 14 |
> |
| 15 |
> Please review the list, it's 800+ packages so I thought about asking for |
| 16 |
> feedback before filing stabilization bugs (I plan to do that in stages |
| 17 |
> of course). |
| 18 |
|
| 19 |
|
| 20 |
This is an excellent idea, and is exactly the kind of thing that we* need |
| 21 |
to be doing to start keeping up with faster release cycles, and managing to |
| 22 |
stay on top of all of the packages that are in the tree without huge |
| 23 |
amounts of developer interaction. |
| 24 |
|
| 25 |
Well done. |
| 26 |
|
| 27 |
J |
| 28 |
|
| 29 |
*IAmNotADev |
Archives