From: "BJ Freeman" <bjf...@free-man.net>
thanks for the update.
thought the PMC are the only ones that can vote on it, not sure why it
can not be discuss in this mailing list if this is truly a community.
Yes, I agree, nothing secret here. Nothing is decided yet anyway, it was just a
pre-discussion which came live there.
Jacques
=========================
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>
Jacques Le Roux sent the following on 3/21/2010 9:40 AM:
Yes a discussion about this subject occured in the PMC private list.
There is a mention about this at
http://cwiki.apache.org/confluence/display/OFBADMIN/ASF+Board+Report+2010-03
Nothing sure yet but something like you suggested
Jacques
From: "BJ Freeman" <bjf...@free-man.net>
that is true.
so maybe use it per release
then consider the new release as new features as you state and start the
processes over again.\
I see this as a way to say this release is in this stage.
this would better inform those that use a release of its age and
stability.
for instance if not enough hours are logged in the alpha and beta stages
it does not get move up.
This goes back to the project management where people would show there
testing efforts and what modules.
=========================
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>
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.
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>
