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.
Nevertheless, we sould not use branch tags to mark releases, as we did with 2.5.2-pl1. :-)
I also wrote to tell you that I'm going to leave good old Mülheim an der Ruhr, Germany, tomorrow. During the next six weeks, my new home will be Monroeville, PA, USA, near Pittsburgh. I probably will be able to access the internet there, but I don't know how much time I can spend on PMA there since I do an internship there.
Regards,
Alexander
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
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
Hi
Original message (Marc Delisle, 18.08.2003 06:28):
now that branch QA_2_5_3 exists, do not forget to commit there the /lang modifications needed in this branch.
Is there any easy way how to commit to HEAD and QA_2_5_3 or do I have to checkout QA_2_5_3, do there changhes and commit there?
Michal
Michal Cihar a écrit:
Hi
Original message (Marc Delisle, 18.08.2003 06:28):
now that branch QA_2_5_3 exists, do not forget to commit there the /lang modifications needed in this branch.
Is there any easy way how to commit to HEAD and QA_2_5_3 or do I have to checkout QA_2_5_3, do there changhes and commit there?
Michal
Michal,
I don't know an easy way, so I do was you suggest.
Marc
-
Marc Delisle -
Michal Cihar -
Rabus