Hello,
* The Trunk version is an unstable version. I think it's better to not
waste time on it, unless you are involved in the development or plan
that test what's coming on.
* It's true that the trunk evolution is controlled by the quality team.
Only 20 people have the right to commit on a trunk branch.
* The branch to be put in production is the stable one. The trunk did
not had testing and rc cycles.
The quality team try to make the trunk the most useable as possible. All
commits on trunk are made by only 20 people. But the trunk remains
unstable for different reasons:
* Some parts are not tested heavily because still in early development
stage and not yet a V1.0: example Business Intelligence
* The quality team validate about 30 merges per day. They don't test
heavily each modification on each platform and environment.
* We can also presume the quality team is not perfect and, as they test
and merge branches, they only test the small part modified by this
branch. It means they will not detect bugs introduced in others parts,
for example: the installation process.
* Some unfinished developments are directly commited in the trunk
because it's easier for the team. A good example, is the new access
right system that touches all modules and took 3 months to be finished.
* We don't guarantee that the trunk is working for every revisions
(remember that we have about 30 revisions per day). A quality team may
commit something and detect after that this cause some troubles.
* The trunk has never been used in production so, before being able to
use it, we need classic testing and release candidates cycles.
As a summary, the trunk represent 1.5 year of development with about 80
full time developers and 20 people in quality team. Everything has been
completly reviewed and improved. Either if the quality team is extremely
good, you can not presume that there is no bug at all before we do
complete test cycles and publish release candidate.
So, the trunk is NOT the most stable current version. The most stable
current version is the stable (4.2) branch in the bazaar, but it's
better to use directly the packaged version which is in the download
section of this website.
Thanks
[EMAIL PROTECTED] wrote:
Pedro,
wrong,
OpenERP follows the principle of branching off development. Stable code is then merged by
a special "Quality Team" into trunk, please read OpenERP commit policy
http://www.openerp.com/wiki/index.php/Community:How_To_Contribute#Bazaar
Therefore the trunk is supposed to be the most stable current version.
Once a milestone has been reached a snapshot of trunk becomes a release.
Again, trunk code can only be committed by the "Quality Team".
Given this self-imposed strategy one can reasonably expect that trunk is
"quality" code which can be installed and which runs bug free. Buggy or
incomplete software should never be committed to trunk.
Such is the btw the policy of many software projects.
If it is indeed so, as you say, that "trunk" is some intermediate , incomplete
software then OpenERP is not following its own self-imposed principles and generally
accepted software development practices.
Geejay
-------------------- m2f --------------------
--
http://www.openerp.com/forum/viewtopic.php?p=25223#25223
-------------------- m2f --------------------
_______________________________________________
Tinyerp-users mailing list
http://tiny.be/mailman/listinfo/tinyerp-users
--
Fabien Pinckaers
CEO Tiny - OpenERP Editor
Chaussée de Namur 40
B-1367 Grand-Rosière
Belgium
Phone: +32.81.81.37.00
Fax: +32.81.73.35.01
Web: http://openerp.com
Great Achievements Start With Tiny Investments
-- Marty, 2005
_______________________________________________
Tinyerp-users mailing list
http://tiny.be/mailman/listinfo/tinyerp-users
