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