s the same set of
functionnalities
And it's not the case for 9.04, 10.04(5?) and trunk.
Jacques
From: "BJ Freeman"
With the focus on stability as defined by software life cycle
That being that once a module had been touched, till it has had
rigorous testing, it is not considered st
pro>
>>
>>
>>
>> Jacques Le Roux sent the following on 3/21/2010 3:22 AM:
>>> The problem with this approach is that it supposes the same set of
>>> functionnalities
>>> And it's not the case for 9.04, 10.04(5?) and trunk.
>>>
>>&
ce a module had been touched, till it has had
rigorous testing, it is not considered stable, I would like to propose a
release life cycle similar to this one.
http://en.wikipedia.org/wiki/Software_release_life_cycle
trunk would be pre-alpha
9.04 beta
10.4 would be alpha.
A vote would by those di
focus on stability as defined by software life cycle
>> That being that once a module had been touched, till it has had
>> rigorous testing, it is not considered stable, I would like to propose a
>> release life cycle similar to this one.
>> http://en.wikipedia.org/wiki/Softw
ill it has had
rigorous testing, it is not considered stable, I would like to propose a
release life cycle similar to this one.
http://en.wikipedia.org/wiki/Software_release_life_cycle
trunk would be pre-alpha
9.04 beta
10.4 would be alpha.
A vote would by those directly involve with each one.
The
With the focus on stability as defined by software life cycle
That being that once a module had been touched, till it has had
rigorous testing, it is not considered stable, I would like to propose a
release life cycle similar to this one.
http://en.wikipedia.org/wiki/Software_release_life_cycle
