Hi Olivier & all!
No problem... so let's say rc3 for 22/07, and a -final against beginning of august ? I will be for a few weeks in germany after the 23/07, but I guess I'll find a phone plug there too, so that won't be a problem :) Just updated the webpage.
OK, that seems fine to me as soon as we all agree that the version I'm working on would be quite different from the current rc because, since I need to rewrite many lines of the code because the (in)famous 'htmlspeciachars' bug, I've decided to also ensure that: - the php code fits PEAR standards... - ...and generates valid XHTML1.0 code.
It's a really huge work and I'm afraid it's difficult to share it. I've done about 60% of the work but I'll be out (for working puprose :() all the next week, so I'm not sure to have completed it before the end of July.
Is it a problem or not?
Regards, 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
Hi all,
I think that we should release 2.2.0 before this big rewrite.
Thousands of persons are already using rc1 or rc2, and we must admit that the problem with fields containing special characters affects only a fraction of them.
Marc
Loïc a écrit :
Hi Olivier & all!
No problem... so let's say rc3 for 22/07, and a -final against beginning of august ? I will be for a few weeks in germany after the 23/07, but I guess I'll find a phone plug there too, so that won't be a problem :) Just updated the webpage.
OK, that seems fine to me as soon as we all agree that the version I'm working on would be quite different from the current rc because, since I need to rewrite many lines of the code because the (in)famous 'htmlspeciachars' bug, I've decided to also ensure that:
- the php code fits PEAR standards...
- ...and generates valid XHTML1.0 code.
It's a really huge work and I'm afraid it's difficult to share it. I've done about 60% of the work but I'll be out (for working puprose :() all the next week, so I'm not sure to have completed it before the end of July.
Is it a problem or not?
Regards, 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
Phpmyadmin-devel mailing list Phpmyadmin-devel@lists.sourceforge.net http://lists.sourceforge.net/lists/listinfo/phpmyadmin-devel
I think that we should release 2.2.0 before this big rewrite.
Thousands of persons are already using rc1 or rc2, and we must admit that the
problem with
fields containing special characters affects only a fraction of them.
Yuk ... Is the bug major (I.E showstopper) or big but easily explanable in a phrase in the readme (as a known bugs feature) ? I agree that a major rewrite should be 2.3 (including new features such as http compression) but a major bug shouldn't be in 2.2 (IMHO) ...
oh well :-o
Alain.
Alain Brissaud a écrit :
I think that we should release 2.2.0 before this big rewrite.
Thousands of persons are already using rc1 or rc2, and we must admit that the
problem with
fields containing special characters affects only a fraction of them.
Yuk ... Is the bug major (I.E showstopper) or big but easily explanable in a phrase in the readme (as a known bugs feature) ? I agree that a major rewrite should be 2.3 (including new features such as http compression) but a major bug shouldn't be in 2.2 (IMHO) ...
oh well :-o
Alain.
If we are talking about bug #439565 (are we?), I think the majority of our users can live with it.
Let's not forget that 2.2.0 could be followed by 2.2.1 in (say) 2 months.
Marc
If we are talking about bug #439565 (are we?), I think the majority of our
users can live with it.
Yes ;-)
Let's not forget that 2.2.0 could be followed by 2.2.1 in (say) 2 months.
Sure, with a CLEAR known bug statement in the readme (I'm not so enlightened about the cases where the bug appears and not) ...
Alain.
Sure, with a CLEAR known bug statement in the readme
<Replying to myself, sorry (off to bed after that...)> Please understand that I'm not anal about this bug, but I answered so many time the question about the quote bug in 2.1.0 in various php forums that I wouldn't like this bug to it to be the focus in the 2.2.0 release (so many new interesting features are there !).
Alain.
-
Alain Brissaud -
Loïc -
Marc Delisle