Bonjour :)
Everything is in the Subject-line... The homepage is currently saying: August 2001: 2.2.0-final.
Do you think we will manage to fix all the current bugs in the 10 next days ? What are the most important show-stoppers for the moment ?
If you are looking for thinks to fix, beside the bugs tracker, also check the http://www.phpwizard.net/phorum/list.php?f=1 forum: there are lots of people "crying" there... : sometimes for little things, but also about important problems.
Otherwise I should maybe already do a pessimistic s/August/September/ on the index.html page... :)
Thanks in advance for your feedback & Have a nice week-end! Olivier
"Olivier M." a écrit :
Bonjour :)
Everything is in the Subject-line... The homepage is currently saying: August 2001: 2.2.0-final.
Do you think we will manage to fix all the current bugs in the 10 next days ? What are the most important show-stoppers for the moment ?
Bonjour !
A few days ago I wrote to the list: -------------- Will it be bug-free? I don't think so.
Will it be the last phpMyAdmin version? I don't think so.
Will 2.2.1 be better? I think yes.
--------------
I know that 2.2.0 is a milestone and that it must be good, but we can't make it perfect.
I will surely not please all developpers, but I think that we can release it now, because: using the most popular browsers, and in day-to-day operations, this version is stable and useful.
I know, we can always say: we must fix this or that bug. For example, it turns out that we can only reproduce the blob corruption bug (not in the bug tracker) with IE 5.0. With IE 5.5 the bug does not occur. So for me, a simple warning in the documentation would be enough.
Regards,
Marc
Hello, Bonjour,
I will surely not please all developpers, but I think that we can release it now, because: using the most popular browsers, and in day-to-day operations, this version is stable and useful.
I agree with Marc ! Please, we must not fall into the trap of the impossible dream of bug-free software. The actual version is perfectly functional. And in case of emergency, we can always deliver a patch.
2.2.0 final must be done.
Armel.
On Sat, 18 Aug 2001, Marc Delisle wrote:
I know, we can always say: we must fix this or that bug. For example, it turns out that we can only reproduce the blob corruption bug (not in the bug tracker) with IE 5.0. With IE 5.5 the bug does not occur. So for me, a simple warning in the documentation
Could somebody put it into the Bug Tracker? Documentation could be a good idea, but does the bug occur under Mozilla as well?
Robin Johnson a écrit :
On Sat, 18 Aug 2001, Marc Delisle wrote:
I know, we can always say: we must fix this or that bug. For example, it turns out that we can only reproduce the blob corruption bug (not in the bug tracker) with IE 5.0. With IE 5.5 the bug does not occur. So for me, a simple warning in the documentation
Could somebody put it into the Bug Tracker? Documentation could be a good idea, but does the bug occur under Mozilla as well?
Now in the Bug Tracker, highest priority!
marc
Bonsoir... :)
On Sat, Aug 18, 2001 at 12:43:08PM -0400, Marc Delisle wrote:
Do you think we will manage to fix all the current bugs in the 10 next days ? What are the most important show-stoppers for the moment ?
A few days ago I wrote to the list:
Will it be bug-free? I don't think so. Will it be the last phpMyAdmin version? I don't think so. Will 2.2.1 be better? I think yes.
I know that 2.2.0 is a milestone and that it must be good, but we can't make it perfect.
ok, right :)
So, let's set a release date, for example in one week ? 2.2.0-final on Sunday 26. August. Today is D - 8.
I will surely not please all developpers, but I think that we can release it now, because: using the most popular browsers, and in day-to-day operations, this version is stable and useful.
Yes, it is pretty stable :) Just tested a lots of things, and only had problems with the user administration pages: adding users is ok, but not editing or setting a db to an user. Could you also make some tries with this page ?
Suggestion for the release plan / tasks list:
[ ] every developper tests so many things as possible, and in both modes (adv auth and std), especially file upload things, and every new features. [ ] redesign of the http://phpmyadmin.sourceforge.net/ page [ ] write a list of major changes/improvements since version 2.1.0 (the changelog is _way_ too long :) [ ] check if the security problems of 2.1.0 are really solved (wouldn't be nice to get a security advisory just after the release...:) [ ] prepare a kind of "press release", which can then be used to announce the release (and reborn) of phpmyadmin to sites like lwn.net, php info pages, etc : something in english in french would be nice, don't you think ? [ ] proof-read the docs [ ] on wednesday or thursday, I'll pack a 2.2.0-cvs package, and ask the people on the users forum to make some last tests just in case... [ ] ... something else ? please add here :)
I'll prepare a draft for the press release the next days, and we can then discuss it here.
Regards from central Switzerland, with an old but good 33600 modem... (rediscovered that ssh -C rules :)
Olivier
On Sat, Aug 18, 2001 at 09:30:42PM +0200, Alain Brissaud wrote:
[ ] ... something else ? please add here :)
... as a reminder : no new features till we go gold !
(-: and no new bugs, please :-) !!!!
Btw, phpMyAdmin is not alone anymore on the market: you can have a look at MyAdmin:
http://www.multimania.com/circuitarnos/myadmin/ http://www.phpinfo.net/?p=commentaires&rub=news_phpinfo&id=416&i...
Lots of good ideas there... for 3.0.0 :)
Olivier
Hi,
before we release the final version, i think we must correct the bug with destroying of binary data in IE and Mozilla. Too many people work with binary tables (images, crypted data and so on)
Regards,
On Sat, 18 Aug 2001, Steve Alberty wrote:
before we release the final version, i think we must correct the bug with destroying of binary data in IE and Mozilla. Too many people work with binary tables (images, crypted data and so on)
Yes, this is one bug i would agree that we need to fix before the release of 2.2.0-final.
-
Alain Brissaud -
Armel FAUVEAU -
Marc Delisle -
Marc Delisle -
Olivier M. -
Robin Johnson -
Steve Alberty