1 |
Dear ebuild maintainers, |
2 |
|
3 |
|
4 |
thirty days is the norm for the minimal period between an ebuilds last |
5 |
non-keywording change while in the tree and the usual call for |
6 |
stabilisation. If you cannot find a pressing reason to push |
7 |
stabilisation forward, then don't ask. In the last few days I have seen |
8 |
several early calls for stabilisation (bugs #217148, #217845, #217841 |
9 |
and #217839 for instance) where no adequate reason was given, in my |
10 |
opinion. |
11 |
|
12 |
A good reason might be an important fix of a severe bug, a fix for a |
13 |
build problem that couldn't be applied to a stable version but had to |
14 |
go into an ebuild revision, or a version/revision that fixes a security |
15 |
problem. |
16 |
|
17 |
On the other hand, maybe these early stabilisation bug reports are a |
18 |
sign of the times and we need to shorten the normal thirty day period, |
19 |
become even more of a cutting edge distro - or at least discuss the |
20 |
options. |
21 |
|
22 |
|
23 |
Kind regards, |
24 |
JeR |
25 |
-- |
26 |
gentoo-dev@l.g.o mailing list |