Hi list,
As a German, I need conventions and guidelines for everything... :o)
Since we now decided to branch out the releases after feature freeze, I
thought we could get some kind of order into our CVS tags and branches.
A good guideline for us could be the PEAR coding standards, again:
http://pear.php.net/manual/en/standards.cvs.php
This would mean, we branch out 2.5.3 into a branch called "QA_2_5_3". From
this branch, we'd release RC2 and later 2.5.3 releases. For the releases,
we'd use tags like "RELEASE_2_5_3RC2", "RELEASE_2_5_3", "RELEASE_2_5_3PL1"
etc. (Let's hope we won't need the last one *g*).
If we wanted to work on a 2.6.0 sometime, we would branch out 2.5.x as
"MAINT_2_5".
I like this notation and think that it could be useful for us.
Nevertheless, we sould not use branch tags to mark releases, as we did with
2.5.2-pl1. :-)
I also wrote to tell you that I'm going to leave good old Mülheim an der
Ruhr, Germany, tomorrow. During the next six weeks, my new home will be
Monroeville, PA, USA, near Pittsburgh.
I probably will be able to access the internet there, but I don't know how
much time I can spend on PMA there since I do an internship there.
Regards,
Alexander
The Internet, 2003-08-17
Greetings,
the phpMyAdmin development team is pleased to announce availability of
the second release candidate for phpMyAdmin 2.5.3.
MySQL 4.1 Note:
phpMyAdmin's MySQL 4.1 support is still experimental
Improvements:
* MySQL 4.1: new page about Character sets and collations
* better support for MySQL charsets
* LIKE in Select sub-page for non-text fields
* optional icons for actions
* better PHP code generation
* possibility to let phpMyAdmin continue execution of a multi-query
statement even though single queries may fail
* possibility to display the result of each query of a multi-query
statement
* display MySQL error code and link to relevant documentation
* Select page: use SELECT * when possible
* Can now bookmark a series of SQL queries
* Relational dropdown field now obey $cfg['LimitChars']
* Relational dropdown now displayed also by value to ease selection
by typing
* FAQ 1.30 about Turck MMCache
* Do not show the "Cookies required" as an error
* New window to browse/choose foreign values when there are more
than 200
Fixes:
* Removed lowercase transformation of SQL
* "Missing..." messages were wrongly displayed
* armascii8 appears twice in the charset list
* InnoDB and multi-columns foreign key
* Confirmation for TRUNCATE statements
* InnoDB and cross-db foreign keys
* Obey fmtType when set to 'none'
* SELECT DISTINCT was broken (MySQL 3)
* User management: MySQL 3 problem with Resource limits
* Could not use a plus sign in ENUM or SET
* Wrong check for DROP DATABASE
* Wrong confirm dialog for "Create PHP Code"
* Avoid a MySQL replication problem
* ENUM field with one value could not be set to NULL
* Export: column header were missing (Excel format)
* Export: problem with LaTeX and relations
* ENUM fields with brackets were truncated
* Wrong "Showing rows..." message when user has put a LIMIT
* IIS and HTTP auth did not work when register_globals=Off
* Export: better handling of special characters
* Export: CSV: some lines could be trimmed
Download/support information on http://www.phpmyadmin.net.
Marc Delisle, for the team.
Hi Marc!
I'd like to use the Patch for browsing foreign values before any RC. What do you think?
Regards,
Garvin.
--
Garvin Hicking | Mediengestalter
www.supergarv.de | #ICQ 21392242
Hi all
could someone with MSIE 6 look at bug #786710? I can not reproduce
this in Mozilla/Konqueror/Opera...
--
Regards
Michal Cihar
http://cihar.liten.cz
Hi,
a Polish version has been put in the translations tracker.
I wonder if we should commit this into the main distribution.
Instead I suggest to create a docs directory on phpmyadmin.net
and put it there. But this implies that I have to remember to
do manual backups of it :)
Opinions?
Marc
Hi,
I suggest to put the
Cookies must be enabled past this point.
message in black, not in red, and like this:
(Cookies must be enabled past this point)
because some users think that they have a problem
and that their cookies are not enabled.
Marc
