Hi all
now when 3.5 is out, do we plan to do one more release of 3.4 series or not? The main reason for this question is whether bug fixes and translation updates should still be pushed to QA_3_4 or it can be safely ignored.
Op 11 april 2012 08:48 heeft Michal Čihař michal@cihar.com het volgende geschreven:
Hi all
now when 3.5 is out, do we plan to do one more release of 3.4 series or not? The main reason for this question is whether bug fixes and translation updates should still be pushed to QA_3_4 or it can be safely ignored.
Hi,
I think we can stop bugfix support for the 3.4 series, now that 3.5 is out. Same for translation updates. We could do one final bugfix release in 3.4 with the bugs that are solved in that branch at the moment, with a final update of the translations at the time of the release.
From then on we would only do security releases in the 3.4 branch.
Kind regards,
Dieter
-- Michal Čihař | http://cihar.com | http://blog.cihar.com
Better than sec? Nothing is better than sec when it comes to monitoring Big Data applications. Try Boundary one-second resolution app monitoring today. Free. http://p.sf.net/sfu/Boundary-dev2dev _______________________________________________ Phpmyadmin-devel mailing list Phpmyadmin-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/phpmyadmin-devel
Hi
Dne Wed, 11 Apr 2012 09:17:49 +0200 Dieter Adriaenssens dieter.adriaenssens@gmail.com napsal(a):
I think we can stop bugfix support for the 3.4 series, now that 3.5 is out. Same for translation updates. We could do one final bugfix release in 3.4 with the bugs that are solved in that branch at the moment, with a final update of the translations at the time of the release. From then on we would only do security releases in the 3.4 branch.
I thought about this approach as well.
Le 2012-04-11 05:38, Michal Čihař a écrit :
Hi
Dne Wed, 11 Apr 2012 09:17:49 +0200 Dieter Adriaenssens dieter.adriaenssens@gmail.com napsal(a):
I think we can stop bugfix support for the 3.4 series, now that 3.5 is out. Same for translation updates. We could do one final bugfix release in 3.4 with the bugs that are solved in that branch at the moment, with a final update of the translations at the time of the release. From then on we would only do security releases in the 3.4 branch.
I thought about this approach as well.
Agreed, I'll proceed today.
On Wed, April 11, 2012 08:48, Michal Cihar wrote:
now when 3.5 is out, do we plan to do one more release of 3.4 series or not? The main reason for this question is whether bug fixes and translation updates should still be pushed to QA_3_4 or it can be safely ignored.
We have a problem with getting 3.5 in Debian because 3.5 contains code that may only be used in non-commercial context, or otherwise a paid licence is needed (highcharts). That's obviously prohibitive for us.
As long as that's not resolved we need to stick wih 3.4; so it really depends on what timeframe we're looking at there if we could make use of further 3.4 updates.
Cheers, Thijs
Hi
Dne Wed, 11 Apr 2012 10:17:50 +0200 "Thijs Kinkhorst" thijs@debian.org napsal(a):
On Wed, April 11, 2012 08:48, Michal Cihar wrote:
now when 3.5 is out, do we plan to do one more release of 3.4 series or not? The main reason for this question is whether bug fixes and translation updates should still be pushed to QA_3_4 or it can be safely ignored.
We have a problem with getting 3.5 in Debian because 3.5 contains code that may only be used in non-commercial context, or otherwise a paid licence is needed (highcharts). That's obviously prohibitive for us.
Obviously we're not alone in this:
https://github.com/Snorby/snorby/issues/70 https://github.com/auxesis/visage/issues/54
Especially second issue looks promising as there seems to be possibility to get Highcharts licensed under GPL.
Le 2012-04-11 07:39, Michal Čihař a écrit :
Hi
Dne Wed, 11 Apr 2012 10:17:50 +0200 "Thijs Kinkhorst" thijs@debian.org napsal(a):
On Wed, April 11, 2012 08:48, Michal Cihar wrote:
now when 3.5 is out, do we plan to do one more release of 3.4 series or not? The main reason for this question is whether bug fixes and translation updates should still be pushed to QA_3_4 or it can be safely ignored.
We have a problem with getting 3.5 in Debian because 3.5 contains code that may only be used in non-commercial context, or otherwise a paid licence is needed (highcharts). That's obviously prohibitive for us.
Obviously we're not alone in this:
https://github.com/Snorby/snorby/issues/70 https://github.com/auxesis/visage/issues/54
Especially second issue looks promising as there seems to be possibility to get Highcharts licensed under GPL.
Michal, who will contact Torstein Hønsi about this?
Le 2012-04-11 08:22, Marc Delisle a écrit :
Le 2012-04-11 07:39, Michal Čihař a écrit :
Hi
Dne Wed, 11 Apr 2012 10:17:50 +0200 "Thijs Kinkhorst" thijs@debian.org napsal(a):
On Wed, April 11, 2012 08:48, Michal Cihar wrote:
now when 3.5 is out, do we plan to do one more release of 3.4 series or not? The main reason for this question is whether bug fixes and translation updates should still be pushed to QA_3_4 or it can be safely ignored.
We have a problem with getting 3.5 in Debian because 3.5 contains code that may only be used in non-commercial context, or otherwise a paid licence is needed (highcharts). That's obviously prohibitive for us.
Obviously we're not alone in this:
https://github.com/Snorby/snorby/issues/70 https://github.com/auxesis/visage/issues/54
Especially second issue looks promising as there seems to be possibility to get Highcharts licensed under GPL.
Michal, who will contact Torstein Hønsi about this?
Also, from [0], "I have only been granted permission to distributed highcharts.js under the GPLv2, not highcharts.src.js."
This means that we should not have renamed highcharts.src.js to highcharts.js because it can create some confusion.
[0] https://github.com/auxesis/visage/commit/58fdbcc9d3b1ccbc8101a1e3fb8cf02303c...
Hi
Dne Wed, 11 Apr 2012 08:28:57 -0400 Marc Delisle marc@infomarc.info napsal(a):
Also, from [0], "I have only been granted permission to distributed highcharts.js under the GPLv2, not highcharts.src.js."
This means that we should not have renamed highcharts.src.js to highcharts.js because it can create some confusion.
Okay, in this case it probably won't really help as I doubt highcharts.js is preferred form of modification according to GPL...
Le 2012-04-11 08:46, Michal Čihař a écrit :
Hi
Dne Wed, 11 Apr 2012 08:28:57 -0400 Marc Delisle marc@infomarc.info napsal(a):
Also, from [0], "I have only been granted permission to distributed highcharts.js under the GPLv2, not highcharts.src.js."
This means that we should not have renamed highcharts.src.js to highcharts.js because it can create some confusion.
Okay, in this case it probably won't really help as I doubt highcharts.js is preferred form of modification according to GPL...
But we could ask to relicense highcharts.src.js.
Le 2012-04-11 09:00, Marc Delisle a écrit :
Le 2012-04-11 08:46, Michal Čihař a écrit :
Hi
Dne Wed, 11 Apr 2012 08:28:57 -0400 Marc Delisle marc@infomarc.info napsal(a):
Also, from [0], "I have only been granted permission to distributed highcharts.js under the GPLv2, not highcharts.src.js."
This means that we should not have renamed highcharts.src.js to highcharts.js because it can create some confusion.
Okay, in this case it probably won't really help as I doubt highcharts.js is preferred form of modification according to GPL...
But we could ask to relicense highcharts.src.js.
I am sending the permission request.
Hi
Dne Wed, 11 Apr 2012 13:24:34 -0400 Marc Delisle marc@infomarc.info napsal(a):
Le 2012-04-11 09:00, Marc Delisle a écrit :
But we could ask to relicense highcharts.src.js.
I am sending the permission request.
Thanks for doing that :-).
-
Dieter Adriaenssens -
Marc Delisle -
Michal Čihař -
Thijs Kinkhorst