| 1 |
Hi, |
| 2 |
|
| 3 |
Arfrever Frehtes Taifersar Arahesis <Arfrever@g.o>: |
| 4 |
|
| 5 |
> Some packages have new releases more than once a month and sometimes |
| 6 |
> it's reasonable to not skip stabilization of any version. Given |
| 7 |
> version of a package is usually no longer tested by users after |
| 8 |
> release of a newer version, so I suggest the following change to the |
| 9 |
> policy of stabilizations: Stabilization of given version of a package |
| 10 |
> can be requested if this version has been in the tree for at least 10 |
| 11 |
> days and a newer version of this package has been added to the tree. |
| 12 |
|
| 13 |
If you do that, you will see arch teams skip those stabilisations in a |
| 14 |
daily rhythm. Honestly, who should do that work? Having every minor |
| 15 |
release stable is a big nuisance for arch workers. |
| 16 |
|
| 17 |
V-Li |
| 18 |
|
| 19 |
-- |
| 20 |
Christian Faulhammer, Gentoo Lisp project |
| 21 |
<URL:http://www.gentoo.org/proj/en/lisp/>, #gentoo-lisp on FreeNode |
| 22 |
|
| 23 |
<URL:http://gentoo.faulhammer.org/> |
Archives