Hi,
I suggest to release 2.3.4-rc1 in one week (Jan 12 on evening).
Marc
-----Original Message----- From: Marc Delisle
Hi,
I suggest to release 2.3.4-rc1 in one week (Jan 12 on evening).
Marc
Marc,
I won't have my work finished until then. Since my todo list about the new server_* pages is rather long and I don't like the idea of releasing unfinished and buggy code, I'd suggest to proceed like we did with 2.2.7 / 2.3.0. This means, we would create a v2.3.4 branch in the CVS tree and remove the server_* files and undo the changes to main.php3 in this branch. We would release 2.3.4-rc1 on Sunday as you suggested. In the MAIN branch, I suggest to increment the minor version number, because the server_* pages contain some major changes that should imho be indicated by a new minor version (2.4.0). Regards,
Alexander
Rabus wrote:
-----Original Message----- From: Marc Delisle
Hi,
I suggest to release 2.3.4-rc1 in one week (Jan 12 on evening).
Marc
Marc,
I won't have my work finished until then. Since my todo list about the new server_* pages is rather long and I don't like the idea of releasing unfinished and buggy code, I'd suggest to proceed like we did with 2.2.7 / 2.3.0. This means, we would create a v2.3.4 branch in the CVS tree and remove the server_* files and undo the changes to main.php3 in this branch. We would release 2.3.4-rc1 on Sunday as you suggested. In the MAIN branch, I suggest to increment the minor version number, because the server_* pages contain some major changes that should imho be indicated by a new minor version (2.4.0). Regards,
Alexander
Alexander,
I realize I am repeating myself, but I would prefer to not branch because it duplicates the bugfix work, and frankly, the current team is too small for the work to do.
I don't think your new code is buggy, and don't forget I am talking about releasing a -rc1: it's a good idea to expose new code for general review before the final release.
I agree with naming it 2.4.0-rc1.
If you insist about adding more things, how much time do you need? We could wait.
About the new server pages: - On the privileges pages, I would like to add this option: "Delete the database which has the same name as the user".
Marc
-----Original Message----- From: Marc Delisle [mailto:delislma@CollegeSherbrooke.qc.ca]
Rabus wrote:
-----Original Message----- From: Marc Delisle
Hi,
I suggest to release 2.3.4-rc1 in one week (Jan 12 on evening).
Marc
Marc,
I won't have my work finished until then. Since my todo
list about the
new server_* pages is rather long and I don't like the idea of releasing unfinished and buggy code, I'd suggest to proceed like we did with 2.2.7 / 2.3.0. This means, we would create a
v2.3.4 branch in
the CVS tree and remove the server_* files and undo the changes to main.php3 in this branch. We would release 2.3.4-rc1 on
Sunday as you
suggested. In the MAIN branch, I suggest to increment the minor version number, because the server_* pages contain some
major changes
that should imho be indicated by a new minor version (2.4.0). Regards,
Alexander
Alexander,
I realize I am repeating myself, but I would prefer to not branch because it duplicates the bugfix work, and frankly, the current team is too small for the work to do.
I just thought, a quick release would be nessecary because 2.3.3-pl1 is not fully compatible with php 4.3.0 which has been released recently (see bug #655153 / patch #647148).
I don't think your new code is buggy, and don't forget I am talking about releasing a -rc1: it's a good idea to expose new code for general review before the final release.
I agree with naming it 2.4.0-rc1.
Fine.
If you insist about adding more things, how much time do you need? We could wait.
What about Feb 2nd for RC1? This would be three weeks later than your schedule.
About the new server pages:
- On the privileges pages, I would like to add this option:
"Delete the database which has the same name as the user".
Good idea, I'll implement it.
Regards,
Alexander
Rabus wrote:
-----Original Message----- From: Marc Delisle [mailto:delislma@CollegeSherbrooke.qc.ca]
Rabus wrote:
-----Original Message----- From: Marc Delisle
Hi,
I suggest to release 2.3.4-rc1 in one week (Jan 12 on evening).
Marc
Marc,
I won't have my work finished until then. Since my todo
list about the
new server_* pages is rather long and I don't like the idea of releasing unfinished and buggy code, I'd suggest to proceed like we did with 2.2.7 / 2.3.0. This means, we would create a
v2.3.4 branch in
the CVS tree and remove the server_* files and undo the changes to main.php3 in this branch. We would release 2.3.4-rc1 on
Sunday as you
suggested. In the MAIN branch, I suggest to increment the minor version number, because the server_* pages contain some
major changes
that should imho be indicated by a new minor version (2.4.0). Regards,
Alexander
Alexander,
I realize I am repeating myself, but I would prefer to not branch because it duplicates the bugfix work, and frankly, the current team is too small for the work to do.
I just thought, a quick release would be nessecary because 2.3.3-pl1 is not fully compatible with php 4.3.0 which has been released recently (see bug #655153 / patch #647148).
For those who upgraded their PHP, the patch #647168 is there. Or they can use the cvs version. But this bug only generates warnings.
I don't think your new code is buggy, and don't forget I am talking about releasing a -rc1: it's a good idea to expose new code for general review before the final release.
I agree with naming it 2.4.0-rc1.
Fine.
If you insist about adding more things, how much time do you need? We could wait.
What about Feb 2nd for RC1? This would be three weeks later than your schedule.
OK.
About the new server pages:
- On the privileges pages, I would like to add this option: "Delete the database which has the same name as the user".
Good idea, I'll implement it.
Thanks.
-
Marc Delisle -
Marc Delisle
-
Rabus