Marc Delisle a écrit:
Rabus a écrit:
Hi list,
As a German, I need conventions and guidelines for everything... :o)
Since we now decided to branch out the releases after feature freeze, I thought we could get some kind of order into our CVS tags and branches. A good guideline for us could be the PEAR coding standards, again:
http://pear.php.net/manual/en/standards.cvs.php
This would mean, we branch out 2.5.3 into a branch called "QA_2_5_3". From this branch, we'd release RC2 and later 2.5.3 releases. For the releases, we'd use tags like "RELEASE_2_5_3RC2", "RELEASE_2_5_3", "RELEASE_2_5_3PL1" etc. (Let's hope we won't need the last one *g*). If we wanted to work on a 2.6.0 sometime, we would branch out 2.5.x as "MAINT_2_5".
I like this notation and think that it could be useful for us.
I agree and I will start with this notation immediately.
Marc
Hi all,
now that branch QA_2_5_3 exists, do not forget to commit there the /lang modifications needed in this branch.
Marc