Hi,
I suggest Sept. 6 for 2.6.0-rc2 release, and probably one week later for 2.6.0-final.
Before -rc2 I plan to work on - removing charset introducers and use CONVERT - bug 1009791
About #1018081, as discussed with Alexander, maybe we should not support MySQL 4.1.0 and 4.1.1 (even though _latin1 won't be there anymore in server_privileges.php).
Also, we will have to make a decision about Safari support before -final.
Other bug reports do not appear show-stoppers to me.
Marc
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi Marc & list,
Marc Delisle wrote:
I suggest Sept. 6 for 2.6.0-rc2 release, and probably one week later for 2.6.0-final.
September 6th for RC2 is fine for me, but I'd like to wait two weeks before we release a final, though.
Before -rc2 I plan to work on
- removing charset introducers and use CONVERT
- bug 1009791
We should also do some testing on the new MySQL 4.1.4-gamma. Although I haven't encountered any (new) problems yet, I think we should ensure that we are really compatible to this one.
About #1018081, as discussed with Alexander, maybe we should not support MySQL 4.1.0
+ 1 for dropping MySQL 4.1.0 support. 4.1.0 is just too experimental and on top of that some core functionalities haven been changed or extended since then, for example the character set environment variables (on which we have to rely) have been added in 4.1.1. Personally, I don't want to write compatibility code for a single experimental alpha version.
and 4.1.1
4.1.1 _should_ be OK, but I'm not sure if we should officially support that version.
Also, we will have to make a decision about Safari support before -final.
I don't like much the idea of working around problems of pre-final testing software.
Other bug reports do not appear show-stoppers to me.
I will also check if there are any possible showstoppers in the list.
Regards,
Alexander M. Turek
PS.: I had to change my PGP key, so please don't be surprised if this key does not mach the one I used in earlier mails.
Alexander M. Turek wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi Marc & list,
Marc Delisle wrote:
I suggest Sept. 6 for 2.6.0-rc2 release, and probably one week later for 2.6.0-final.
September 6th for RC2 is fine for me, but I'd like to wait two weeks before we release a final, though.
OK for 2 weeks.
Before -rc2 I plan to work on
- removing charset introducers and use CONVERT
- bug 1009791
This is done.
We should also do some testing on the new MySQL 4.1.4-gamma. Although I haven't encountered any (new) problems yet, I think we should ensure that we are really compatible to this one.
I did not see any problems under 4.1.4 here.
About #1018081, as discussed with Alexander, maybe we should not support MySQL 4.1.0
- 1 for dropping MySQL 4.1.0 support. 4.1.0 is just too experimental and
on top of that some core functionalities haven been changed or extended since then, for example the character set environment variables (on which we have to rely) have been added in 4.1.1. Personally, I don't want to write compatibility code for a single experimental alpha version.
and 4.1.1
4.1.1 _should_ be OK, but I'm not sure if we should officially support that version.
Also, we will have to make a decision about Safari support before -final.
I don't like much the idea of working around problems of pre-final testing software.
I did not mean that the current Safari is not final, I meant supporting Safari in phpMyAdmin 2.6-0 (final). Well, maybe Safari 1.2.3 final is not so final, after all :)
Other bug reports do not appear show-stoppers to me.
I will also check if there are any possible showstoppers in the list.
Regards,
Alexander M. Turek
Hi
On 01.09.2004 13:34 -0400, Marc Delisle wrote:
I suggest Sept. 6 for 2.6.0-rc2 release, and probably one week later for 2.6.0-final.
I'd choose longer delay before final, how about two weeks?
Also, we will have to make a decision about Safari support before -final.
Forget about it, I played a bit with this crap and they use quite old KHTML engine there and hope they'll upgrade sometimes. If it works fine in Konqueror, it should work also in Safari, but that's not true for now.
Other bug reports do not appear show-stoppers to me.
I also don't see anything important.
Michal Čihař wrote:
Hi
On 01.09.2004 13:34 -0400, Marc Delisle wrote:
I suggest Sept. 6 for 2.6.0-rc2 release, and probably one week later for 2.6.0-final.
I'd choose longer delay before final, how about two weeks?
OK
Also, we will have to make a decision about Safari support before -final.
Forget about it, I played a bit with this crap and they use quite old KHTML engine there and hope they'll upgrade sometimes. If it works fine in Konqueror, it should work also in Safari, but that's not true for now.
Thanks Michal for your comments about Safari. We will have to add a warning somewhere (in the announcement, in the FAQ) about it, unless we get patches (that do not interfere with other browsers).
Other bug reports do not appear show-stoppers to me.
I also don't see anything important.
I smell 2.6.0-rc2 coming tomorrow :)
Marc
Marc Delisle a écrit :
Michal Čihař wrote:
Hi
On 01.09.2004 13:34 -0400, Marc Delisle wrote:
I suggest Sept. 6 for 2.6.0-rc2 release, and probably one week later for 2.6.0-final.
I'd choose longer delay before final, how about two weeks?
OK
Just an update: we had a relatively calm week, with minor fixes merged. It looks promising for a 2.6.0 release on September 19th.
Marc
-
Alexander M. Turek -
Marc Delisle -
Michal Čihař