On Tue, Mar 2, 2010 at 9:41 AM, William Hubbs wrote:
> On Tue, Mar 02, 2010 at 09:30:18AM +0100, Justin wrote:
>> On 01/03/10 16:39, Lie Ryan wrote:
>> > I've found a few people referencing to a "30-day stabilization policy"
>> > which basically says a package must be at least 30-days-old to be
>>
Lie Ryan said:
> I've been running several ~arch-ed packages that appears to be compile
> and runs fine on my machine and would like to vote them for
> stabilization. Is it enough to just open a bug issue and pray that the
> arch manager would notice?
The general policy is here:
http://devmanual
On Tue, Mar 02, 2010 at 09:30:18AM +0100, Justin wrote:
> On 01/03/10 16:39, Lie Ryan wrote:
> > I've found a few people referencing to a "30-day stabilization policy"
> > which basically says a package must be at least 30-days-old to be
> > considered for stabilization, but is there any document t
On 01/03/10 16:39, Lie Ryan wrote:
> I've found a few people referencing to a "30-day stabilization policy"
> which basically says a package must be at least 30-days-old to be
> considered for stabilization, but is there any document that serves as
> an official guideline/checklist on how to consid
On 01/03/10 16:39, Lie Ryan wrote:
> I've found a few people referencing to a "30-day stabilization policy"
> which basically says a package must be at least 30-days-old to be
> considered for stabilization, but is there any document that serves as
> an official guideline/checklist on how to consid
On Monday 01 March 2010 17:39:47 Lie Ryan wrote:
> I've found a few people referencing to a "30-day stabilization policy"
> which basically says a package must be at least 30-days-old to be
> considered for stabilization, but is there any document that serves as
> an official guideline/checklist on
6 matches
Mail list logo
