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.

Jacques

From: "BJ Freeman" <bjf...@free-man.net>
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

trunk would be pre-alpha
9.04  beta
10.4 would be alpha.
A vote would by those directly involve with each one.
The problem is what would constitute rigorous testing, to certify that
code to move to the next level.. This would alleviate misunderstanding
about what
Release and RTM means.

Yes I am trying to get away from the  No compile errors means stable code.
Also what the design scope and goal is.

=========================
BJ Freeman
http://bjfreeman.elance.com
Strategic Power Office with Supplier Automation 
<http://www.businessesnetwork.com/automation/viewforum.php?f=93>
Specialtymarket.com <http://www.specialtymarket.com/>

Systems Integrator-- Glad to Assist

Chat  Y! messenger: bjfr33man
Linkedin
<http://www.linkedin.com/profile?viewProfile=&key=1237480&locale=en_US&trk=tab_pro>



Reply via email to