Hi List!
I noticed that the CVS link on the phpMyAdmin website to the current CVS version is labelled as "CVS version 2.2.7-cvs". Shouldn't this be "CVS version 2.3.0-cvs"?
My fault! But I wonder if we'd not better work on two branches in the CVS tree or on two CVS trees: one where we just pursuit the fixing of little bugs of the 2.2.6 release (2.2.7-cvs then), and the other one where we start the "big work" for 2.3.0.
Any thought?
Loïc
______________________________________________________________________________ ifrance.com, l'email gratuit le plus complet de l'Internet ! vos emails depuis un navigateur, en POP3, sur Minitel, sur le WAP... http://www.ifrance.com/_reloc/email.emailif
I would not like to branch, because:
- my time is limited and I don't like the idea of applying the corrections to 2 trees
- 2.2.6 is stable and useful as is
- we can always put individual patches on phpmyadmin.net for important 2.2.6 corrections
- we should concentrate on 2.3.0 to be more productive and focused
"Loïc" a écrit :
Hi List!
I noticed that the CVS link on the phpMyAdmin website to the current CVS version is labelled as "CVS version 2.2.7-cvs". Shouldn't this be "CVS version 2.3.0-cvs"?
My fault! But I wonder if we'd not better work on two branches in the CVS tree or on two CVS trees: one where we just pursuit the fixing of little bugs of the 2.2.6 release (2.2.7-cvs then), and the other one where we start the "big work" for 2.3.0.
Any thought?
Loïc and List,
we should decide about working in 1 branch or 2, because right now we are stalled: we can't start big changes if we have to release a 2.2.7 in a few weeks.
On the other hand, we don't need to work 3 months on a 2.3.0: even if the tbl_properties split is not completed, we can release it, say in 6 weeks. We just have to be sure that the new cfg variables are in place. We now have 3 volunteers on this, so better start soon!
Marc Delisle a écrit :
I would not like to branch, because:
my time is limited and I don't like the idea of applying the corrections to 2 trees
2.2.6 is stable and useful as is
we can always put individual patches on phpmyadmin.net for important 2.2.6 corrections
we should concentrate on 2.3.0 to be more productive and focused
"Loïc" a écrit :
Hi List!
I noticed that the CVS link on the phpMyAdmin website to the current CVS version is labelled as "CVS version 2.2.7-cvs". Shouldn't this be "CVS version 2.3.0-cvs"?
My fault! But I wonder if we'd not better work on two branches in the CVS tree or on two CVS trees: one where we just pursuit the fixing of little bugs of the 2.2.6 release (2.2.7-cvs then), and the other one where we start the "big work" for 2.3.0.
Any thought?
-- Marc Delisle
Phpmyadmin-devel mailing list Phpmyadmin-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/phpmyadmin-devel
Marc,
why shall we hurry with 2.3.0? Even if we needed 3 months, why shouldn't we take the ime we need? I really don't like the idea of half-finished software. We are not Microsoft... :o)
imho we should open a bugfix branch where we only commit really important bugfixes that don't go too deep into the code, like the russian laguage file for instance. And in a few weeks, we'll release it as 2.2.7 and close the branch. If you have not time to work on a second brach, it doesn't matter. It's not necessary that we all work on the bugfix branch, Loïc and me could do it (is it all right for you, Loïc?)... As a base for the bugfix branch, we should use the files of our 2.2.6 release since I already committed patches I'm currently working on...
Alexander
Alexander,
I did not said we should hurry for 2.3.0. What we will release as 2.3.0 will be tested, but 2.3.0 won't have all the 50 new features requested :)
We once had 2 branches for this projects and I did not like the experience: too much work applying fixes in both branches, and possibly having 2 versions for the same fix. Testing 2 branches, etc.
But I did not decide anything, I just told you my opinion.
Also, I think that 2.2.6 is quite useful in itself, and the bugs that will show up will be light and can wait some weeks.
Rabus a écrit :
Marc,
why shall we hurry with 2.3.0? Even if we needed 3 months, why shouldn't we take the ime we need? I really don't like the idea of half-finished software. We are not Microsoft... :o)
imho we should open a bugfix branch where we only commit really important bugfixes that don't go too deep into the code, like the russian laguage file for instance. And in a few weeks, we'll release it as 2.2.7 and close the branch. If you have not time to work on a second brach, it doesn't matter. It's not necessary that we all work on the bugfix branch, Loïc and me could do it (is it all right for you, Loïc?)... As a base for the bugfix branch, we should use the files of our 2.2.6 release since I already committed patches I'm currently working on...
Alexander
Phpmyadmin-devel mailing list Phpmyadmin-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/phpmyadmin-devel
-
Lo�c -
Marc Delisle -
Rabus