Re: [gentoo-dev] Early stabilisation

2008-04-17 Thread Vlastimil Babka
Samuli Suominen wrote: Wed, 16 Apr 2008 12:09:24 -0700 Chris Gianelloni [EMAIL PROTECTED] kirjoitti: On Wed, 2008-04-16 at 11:49 +0200, Vlastimil Babka wrote: thirty days is the norm for the minimal period between an ebuilds last It is the norm. It is not a requirement. In fact, it is

Re: [gentoo-dev] Early stabilisation

2008-04-17 Thread Jeroen Roovers
On Thu, 17 Apr 2008 15:33:17 +0300 Samuli Suominen [EMAIL PROTECTED] wrote: Thu, 17 Apr 2008 09:43:59 +0200 Vlastimil Babka [EMAIL PROTECTED] kirjoitti: Okay. So we can just agree it's better if the maintainer tells his reasons when opening the bug, to spare the later clarifications?

Re: [gentoo-dev] Early stabilisation

2008-04-17 Thread Jeroen Roovers
On Thu, 17 Apr 2008 15:33:17 +0300 Samuli Suominen [EMAIL PROTECTED] wrote: It works. Do it. Oh by the way. This isn't directed toward you personally, but I personally detest this do it attitude. You wouldn't say that to my face, would you? (Trust me, you would regret it.) :) JeR --

Re: [gentoo-dev] Early stabilisation

2008-04-17 Thread Santiago M. Mola
On Thu, Apr 17, 2008 at 2:33 PM, Samuli Suominen [EMAIL PROTECTED] wrote: Thu, 17 Apr 2008 09:43:59 +0200 Vlastimil Babka [EMAIL PROTECTED] kirjoitti: Okay. So we can just agree it's better if the maintainer tells his reasons when opening the bug, to spare the later clarifications? It

Re: [gentoo-dev] Early stabilisation

2008-04-17 Thread Thomas Anderson
On Thu, Apr 17, 2008 at 09:40:22PM +0200, Santiago M. Mola wrote: On Thu, Apr 17, 2008 at 2:33 PM, Samuli Suominen [EMAIL PROTECTED] wrote: Thu, 17 Apr 2008 09:43:59 +0200 Vlastimil Babka [EMAIL PROTECTED] kirjoitti: Okay. So we can just agree it's better if the maintainer tells his

Re: [gentoo-dev] Early stabilisation

2008-04-16 Thread Vlastimil Babka
Jeroen Roovers wrote: Dear ebuild maintainers, thirty days is the norm for the minimal period between an ebuilds last non-keywording change while in the tree and the usual call for stabilisation. If you cannot find a pressing reason to push stabilisation forward, then don't ask. In the

Re: [gentoo-dev] Early stabilisation

2008-04-16 Thread Chris Gianelloni
On Wed, 2008-04-16 at 11:49 +0200, Vlastimil Babka wrote: thirty days is the norm for the minimal period between an ebuilds last It is the norm. It is not a requirement. In fact, it is specifically a guideline rather than a hard rule. It is up to the maintainer's discretion when to ask for

Re: [gentoo-dev] Early stabilisation

2008-04-16 Thread Samuli Suominen
Wed, 16 Apr 2008 12:09:24 -0700 Chris Gianelloni [EMAIL PROTECTED] kirjoitti: On Wed, 2008-04-16 at 11:49 +0200, Vlastimil Babka wrote: thirty days is the norm for the minimal period between an ebuilds last It is the norm. It is not a requirement. In fact, it is specifically a

[gentoo-dev] Early stabilisation

2008-04-15 Thread Jeroen Roovers
Dear ebuild maintainers, thirty days is the norm for the minimal period between an ebuilds last non-keywording change while in the tree and the usual call for stabilisation. If you cannot find a pressing reason to push stabilisation forward, then don't ask. In the last few days I have seen