[Phpmyadmin-devel] seperate branch for solving elaborate bug?
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&atid... [1] https://sourceforge.net/tracker/?func=detail&aid=3136655&group_id=23067&atid... [2] https://sourceforge.net/tracker/?func=detail&aid=3076692&group_id=23067&atid... [3] https://sourceforge.net/tracker/index.php?func=detail&aid=3135414&group_id=2... [4] http://codicesoftware.blogspot.com/2010/11/linus-on-branching.html Kind regards, Dieter
Dieter Adriaenssens a écrit :
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.
I'm a bit confused. Since this feature does not exist in 3.3 (and will not exist because 3.3 won't get new features), are these bugs really related to 3.3.x? -- Marc Delisle http://infomarc.info
Hi, 2010/12/13 Marc Delisle <marc@infomarc.info>:
Dieter Adriaenssens a écrit :
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.
I'm a bit confused. Since this feature does not exist in 3.3 (and will not exist because 3.3 won't get new features), are these bugs really related to 3.3.x?
Does it apply to 3.4.x then? As a new feature? But then the same logic applies, I just want to avoid that, if the fixes are done in QA_3_4 (which does not exist at this moment), not all mentioned bugs are solved before the next stable release? Or should this be done in 3.5-dev (once QA_3_4 is created and master is equal to 3.5-dev? I have the feeling I'm making things complicated. :p Greets, Dieter
-- Marc Delisle http://infomarc.info
------------------------------------------------------------------------------ Lotusphere 2011 Register now for Lotusphere 2011 and learn how to connect the dots, take your collaborative environment to the next level, and enter the era of Social Business. http://p.sf.net/sfu/lotusphere-d2d _______________________________________________ Phpmyadmin-devel mailing list Phpmyadmin-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/phpmyadmin-devel
-- Groetjes, Dieter Adriaenssens
Dieter Adriaenssens a écrit :
Hi,
2010/12/13 Marc Delisle <marc@infomarc.info>:
Dieter Adriaenssens a écrit :
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. I'm a bit confused. Since this feature does not exist in 3.3 (and will not exist because 3.3 won't get new features), are these bugs really related to 3.3.x?+
Does it apply to 3.4.x then? As a new feature? But then the same logic applies, I just want to avoid that, if the fixes are done in QA_3_4 (which does not exist at this moment), not all mentioned bugs are solved before the next stable release? Or should this be done in 3.5-dev (once QA_3_4 is created and master is equal to 3.5-dev?
I have the feeling I'm making things complicated. :p
If these bugs cannot be reproduced in 3.3, please do not use "3.3.8" as group when describing these bugs. There are bugs in all releases, even when named "stable". Of course we try to balance the importance of the bug (if it's known before a release) to avoid a release with "big" bugs in it. We agreed that we won't add features to master for now because we are stabilizing it for 3.4. When it's time for 3.4.0-rc1 (release candidate) then MAINT_3_4_0 will start and it will be time to add features to master. Meanwhile you could start a new branch (even a public branch) to work on these features. See [0]. [0] http://wiki.phpmyadmin.net/pma/Devel:Git#Working_on_new_features -- Marc Delisle http://infomarc.info
Hi, 2010/12/13 Marc Delisle <marc@infomarc.info>:
Dieter Adriaenssens a écrit :
Hi,
2010/12/13 Marc Delisle <marc@infomarc.info>:
Dieter Adriaenssens a écrit :
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. I'm a bit confused. Since this feature does not exist in 3.3 (and will not exist because 3.3 won't get new features), are these bugs really related to 3.3.x?+
Does it apply to 3.4.x then? As a new feature? But then the same logic applies, I just want to avoid that, if the fixes are done in QA_3_4 (which does not exist at this moment), not all mentioned bugs are solved before the next stable release? Or should this be done in 3.5-dev (once QA_3_4 is created and master is equal to 3.5-dev?
I have the feeling I'm making things complicated. :p
If these bugs cannot be reproduced in 3.3, please do not use "3.3.8" as group when describing these bugs.
Fixed.
There are bugs in all releases, even when named "stable". Of course we try to balance the importance of the bug (if it's known before a release) to avoid a release with "big" bugs in it.
I agree. And this example is a case of bugs know before (potential) release. ;)
We agreed that we won't add features to master for now because we are stabilizing it for 3.4. When it's time for 3.4.0-rc1 (release candidate) then MAINT_3_4_0 will start and it will be time to add features to master.
I wanted to be sure, so I asked.
Meanwhile you could start a new branch (even a public branch) to work on these features. See [0].
[0] http://wiki.phpmyadmin.net/pma/Devel:Git#Working_on_new_features
Done, thanks for the advice. Greets, Dieter
participants (2)
-
Dieter Adriaenssens -
Marc Delisle