Developers December 2010

developers@phpmyadmin.net

9 participants
17 discussions

Re: [Phpmyadmin-devel] [ phpmyadmin-Bugs-3119882 ] Visual presentation of warning message

by Herman van Rink

On 06-12-10 16:08, SourceForge.net wrote: > https://sourceforge.net/tracker/?func=detail&atid=377408&aid=3119882&group_… I'd like to hear some opinions on how 'loud' a warning for a 'slow' feature should be. -- Met vriendelijke groet / Regards, Herman van Rink Initfour websolutions

13 years, 7 months

[Phpmyadmin-devel] XML support for exporting

by AAMIR KHAN

There's option to export as XML in db_export.php while not in server_export.php in 3.4.0-aplha release... and this is same for previous stable releases too.. Why it is like this? why whole server can't be exported as XML file? ___ Regards systemw0rm

13 years, 7 months

[Phpmyadmin-devel] seperate branch for solving elaborate bug?

by Dieter Adriaenssens

Hi all, Looking into the XML export functionality, some known issues (solved for SQL export) apply to XML export too : bug #3136658 : export functions/routines before tables [0] bug #3136655 : export view of view [1] bug #3076692 : events are not exported [2] At this moment these bugs cannot be reproduced because 'export schema structure' is not available as an option when exporting as xml, but before enabling and releasing (patch #3135414 [3] ) this, I think all the mentioned bugs should be solved, because it's not a good idea to introduce known bugs with a stable release. Now, as there is no real development branch at this moment, I was thinking it might be a good idea to create a separate branch for these related bugs, that can be merged into the QA_3_3/QA_3_4/master (or whichever branch is current then) once all the work is done. I know I can create a local development branch on my system, but then nobody else that would work on the same set of bugs, can keep current with development that was done. What do you think? BTW: I'm a bit inspired by a recent post of Linus about branching [4]. I realize this does not completely apply to what I'm suggesting here, but it got me thinking anyway. As I see it now, there is no real way of 'picking' features that go into a release, because everything is added to a development branch. Forgive me if I'm potentially overcomplicating things. ;) [0] https://sourceforge.net/tracker/?func=detail&aid=3136658&group_id=23067&ati… [1] https://sourceforge.net/tracker/?func=detail&aid=3136655&group_id=23067&ati… [2] https://sourceforge.net/tracker/?func=detail&aid=3076692&group_id=23067&ati… [3] https://sourceforge.net/tracker/index.php?func=detail&aid=3135414&group_id=… [4] http://codicesoftware.blogspot.com/2010/11/linus-on-branching.html Kind regards, Dieter

13 years, 7 months

[Phpmyadmin-devel] phpMyAdmin 3.4.0-beta1 is released

by Marc Delisle

Welcome to the first beta release of phpMyAdmin 3.4.0. This release contains new features, especially: * User preferences * Relation schema export to multiple formats * ENUM/SET editor * Simplified interface for export/import * AJAXification of some parts * Charts * Visual query builder Details will appear on http://phpmyadmin.net. In a hurry? you can visit http://sourceforge.net/projects/phpmyadmin to download. Marc Delisle, for the team

13 years, 7 months

[Phpmyadmin-devel] Adding xz to download options

by Michal Čihař

Hi all any opinions to provide xz compressed tarballs? It has better compression ratio that gzip or bzip2, while it requires similar resources for decompression as gzip (and this much less than bzip2). The script for creating releases and website is prepared for this, all what needs to be done is ensuring that xz-utils are installed on system, where relases are being done and enabling it in script creating release. You can find more information on xz here: http://tukaani.org/xz/ -- Michal Čihař | http://cihar.com | http://blog.cihar.com

13 years, 7 months

[Phpmyadmin-devel] QA_3_4 too soon

by Marc Delisle

Hi, I realize that I started QA_3_4 too soon. It only needs to begin when 3.4.0 (final) is released. I'll remove it. >From now on we should focus on stabilizing MAINT_3_4_0; new features would go to master only. If it makes sense to fix a bug in QA_3_3 (for 3.3.9) we do it; then we merge to MAINT_3_4_0 and master. -- Marc Delisle http://infomarc.info

13 years, 7 months

Re: [Phpmyadmin-devel] [ phpmyadmin-Patches-3055886 ] (ok 3.4) Left frame table filter visibility config option

by Herman van Rink

On 30-11-10 15:24, SourceForge.net wrote: > Patches item #3055886, was opened at 2010-08-30 10:21 > Message generated for change (Comment added) made by kai-schaetzl > You can respond by visiting: > https://sourceforge.net/tracker/?func=detail&atid=377410&aid=3055886&group_… > I think we could make this last suggestion happen, it makes sense. What would be a sensible default ... 20? And would it not be confusing for users? -- Met vriendelijke groet / Regards, Herman van Rink Initfour websolutions

13 years, 7 months

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

Developers December 2010