Re: [Qgis-developer] Freeze on release-2_8 branch
Blog post published: http://blog.qgis.org/2015/08/06/point-release-qgis-2-8-3-wien-is-ready/ Best wishes, Anita On Thu, Aug 6, 2015 at 6:08 PM, Paolo Cavallini cavall...@faunalia.it wrote: Il 06/08/2015 17:28, Anita Graser ha scritto: Sure I guess we can. Didn't remember that announcement ;) so probably our announcements could be more visible ;) thanks. -- Paolo Cavallini - www.faunalia.eu QGIS PostGIS courses: http://www.faunalia.eu/training.html ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Freeze on release-2_8 branch
Il 05/08/2015 22:35, Anita Graser ha scritto: Just let me know if you want me to publish the announcement on the blog as well once you've written it or if you prefer doing that yourself. by you do you mean Juergen, or myself? I do not mind whichever way, I think we can reuse the standard announcement, just stripping down useless parts. All the best, and thanks. -- Paolo Cavallini - www.faunalia.eu QGIS PostGIS courses: http://www.faunalia.eu/training.html ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Freeze on release-2_8 branch
On Thu, Aug 6, 2015 at 10:16 AM, Paolo Cavallini cavall...@faunalia.it wrote: Il 05/08/2015 22:35, Anita Graser ha scritto: Just let me know if you want me to publish the announcement on the blog as well once you've written it or if you prefer doing that yourself. by you do you mean Juergen, or myself? I meant you, Paolo :) Best wishes, Anita ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Freeze on release-2_8 branch
Il 06/08/2015 10:29, Anita Graser ha scritto: On Thu, Aug 6, 2015 at 10:16 AM, Paolo Cavallini cavall...@faunalia.it mailto:cavall...@faunalia.it wrote: Il 05/08/2015 22:35, Anita Graser ha scritto: Just let me know if you want me to publish the announcement on the blog as well once you've written it or if you prefer doing that yourself. by you do you mean Juergen, or myself? I meant you, Paolo :) Hi, can't we just reuse: https://lists.osgeo.org/pipermail/qgis-developer/2015-May/037717.html we just have to update: https://github.com/qgis/QGIS/compare/final-2_8_1...final-2_8_2 with the new comparison. All the best. -- Paolo Cavallini - www.faunalia.eu QGIS PostGIS courses: http://www.faunalia.eu/training.html ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Freeze on release-2_8 branch
On Thu, Aug 6, 2015 at 4:52 PM, Paolo Cavallini cavall...@faunalia.it wrote: Il 06/08/2015 10:29, Anita Graser ha scritto: On Thu, Aug 6, 2015 at 10:16 AM, Paolo Cavallini cavall...@faunalia.it mailto:cavall...@faunalia.it wrote: Il 05/08/2015 22:35, Anita Graser ha scritto: Just let me know if you want me to publish the announcement on the blog as well once you've written it or if you prefer doing that yourself. by you do you mean Juergen, or myself? I meant you, Paolo :) Hi, can't we just reuse: https://lists.osgeo.org/pipermail/qgis-developer/2015-May/037717.html we just have to update: https://github.com/qgis/QGIS/compare/final-2_8_1...final-2_8_2 with the new comparison. Sure I guess we can. Didn't remember that announcement ;) Best wishes, Anita ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Freeze on release-2_8 branch
Hi Paolo, On Mon, Aug 3, 2015 at 6:40 PM, Paolo Cavallini cavall...@faunalia.it wrote: I also think point releases should be announced (just with a shorter announcement, with less emphasis). I'll be happy of taking care of this. I believe this should be done with the same procedure as for the normal release announcements. So, Juergen, should I do this from now on, or what do you prefer? Just let me know if you want me to publish the announcement on the blog as well once you've written it or if you prefer doing that yourself. Best wishes, Anita ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Freeze on release-2_8 branch
On 03-08-15 09:01, Paolo Cavallini wrote: Il 30/07/2015 01:05, Nyall Dawson ha scritto: On a semi-related theme, we really need a core QGIS update available plugin. I suspect there's a ton of users still on 2.8.0/.1/2.8 just due to not knowing there's a new version out. This could also be really handy for tracking stats of users... Hi Nyall, thanks for raising this. We have been discussing about it several times in the past, and never got round it mainly because of privacy concerns, I believe. I'd be in favour of setting it up, of course asking consent from the user during installation. Do you have an idea of how difficult could it be? Moved this discussion deserves a separate thread... Regards, Richard Duivenvoorde ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Freeze on release-2_8 branch
Il 30/07/2015 01:05, Nyall Dawson ha scritto: On a semi-related theme, we really need a core QGIS update available plugin. I suspect there's a ton of users still on 2.8.0/.1/2.8 just due to not knowing there's a new version out. This could also be really handy for tracking stats of users... Hi Nyall, thanks for raising this. We have been discussing about it several times in the past, and never got round it mainly because of privacy concerns, I believe. I'd be in favour of setting it up, of course asking consent from the user during installation. Do you have an idea of how difficult could it be? All the best. -- Paolo Cavallini - www.faunalia.eu QGIS PostGIS courses: http://www.faunalia.eu/training.html ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Freeze on release-2_8 branch
Il 30/07/2015 12:05, Sandro Santilli ha scritto: On Thu, Jul 30, 2015 at 10:07:32AM +0200, Jürgen E. Fischer wrote: We need to be noisy about point releases, too? It's all on github anyway. Can't sales or marketing take care of that? ;) Personally, I would not consider announcing a bugfix release as noise. That said, if a sales marketing dept exists, this is surely something it should take care of :) Hi all. I also think point releases should be announced (just with a shorter announcement, with less emphasis). I'll be happy of taking care of this. I believe this should be done with the same procedure as for the normal release announcements. So, Juergen, should I do this from now on, or what do you prefer? All the best. -- Paolo Cavallini - www.faunalia.eu QGIS PostGIS courses: http://www.faunalia.eu/training.html ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Freeze on release-2_8 branch
Hi, On Thu, 30. Jul 2015 at 09:05:11 +1000, Nyall Dawson wrote: They were both backported to 2.8.3 (thanks Jürgen!). I assume the release announcement is waiting on the packages being built and available for the major platforms. We need to be noisy about point releases, too? It's all on github anyway. Can't sales or marketing take care of that? ;) Jürgen -- Jürgen E. Fischer norBIT GmbH Tel. +49-4931-918175-31 Dipl.-Inf. (FH) Rheinstraße 13 Fax. +49-4931-918175-50 Software Engineer D-26506 Norden http://www.norbit.de QGIS release manager (PSC) GermanyIRC: jef on FreeNode signature.asc Description: Digital signature ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Freeze on release-2_8 branch
On Wed, Jul 22, 2015 at 08:09:49PM +1000, Nyall Dawson wrote: On 14 July 2015 at 00:04, Matthias Kuhn matth...@opengis.ch wrote: Hi On Mon, Jul 13, 2015 at 03:44:28PM +0200, Sandro Santilli wrote: On Mon, Jul 13, 2015 at 03:30:38PM +0200, Matthias Kuhn wrote: Regarding this, I would propose to put the freeze in place as of Tue, Jul 14, 12:00 UTC And - presuming there are no regressions found - 2.8.3 will be tagged on Tue, Jul, 28. +1, but I'd avoid the word freeze as it may be confusing. We're basically asking all developers to refrain from pushing more backports in that branch until 2.8.3 is released. Oh, forgot to mention, we're also asking developers to _test_ the branch, or it would make no sense to wait another week, right ? It might actually help to make an official call for testing on the users list too. I'm sure many will be happy to test the next stable release before it comes out (either from snapshot or directly from git). I've submitted by make Experimental already. --strk; +1 I planned to send a tweet tomorrow but any widespread call for testing will be good (but mainly by power users and organizations who actually use it. We cannot put that also on the developers back) I'd really like to backport c8dcf97 (critical for 2.8.3 IMO) and a1a8d1b (nice to have for 2.8.3), but don't want to reset the countdown now. Is there anyway around this? I noticed 2.8.3 was tagged on July 28, as anticipated, but did not see any announcement mail. Is that waiting for some form of packaging ? Also, were those two commits backported ? There's no trace of those hashes in the history of 2.8 branch. --strk; ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Freeze on release-2_8 branch
On 30 Jul 2015 8:44 am, Sandro Santilli s...@keybit.net wrote: On Wed, Jul 22, 2015 at 08:09:49PM +1000, Nyall Dawson wrote: On 14 July 2015 at 00:04, Matthias Kuhn matth...@opengis.ch wrote: Hi On Mon, Jul 13, 2015 at 03:44:28PM +0200, Sandro Santilli wrote: On Mon, Jul 13, 2015 at 03:30:38PM +0200, Matthias Kuhn wrote: Regarding this, I would propose to put the freeze in place as of Tue, Jul 14, 12:00 UTC And - presuming there are no regressions found - 2.8.3 will be tagged on Tue, Jul, 28. +1, but I'd avoid the word freeze as it may be confusing. We're basically asking all developers to refrain from pushing more backports in that branch until 2.8.3 is released. Oh, forgot to mention, we're also asking developers to _test_ the branch, or it would make no sense to wait another week, right ? It might actually help to make an official call for testing on the users list too. I'm sure many will be happy to test the next stable release before it comes out (either from snapshot or directly from git). I've submitted by make Experimental already. --strk; +1 I planned to send a tweet tomorrow but any widespread call for testing will be good (but mainly by power users and organizations who actually use it. We cannot put that also on the developers back) I'd really like to backport c8dcf97 (critical for 2.8.3 IMO) and a1a8d1b (nice to have for 2.8.3), but don't want to reset the countdown now. Is there anyway around this? I noticed 2.8.3 was tagged on July 28, as anticipated, but did not see any announcement mail. Is that waiting for some form of packaging ? Also, were those two commits backported ? There's no trace of those hashes in the history of 2.8 branch. They were both backported to 2.8.3 (thanks Jürgen!). I assume the release announcement is waiting on the packages being built and available for the major platforms. On a semi-related theme, we really need a core QGIS update available plugin. I suspect there's a ton of users still on 2.8.0/.1/2.8 just due to not knowing there's a new version out. This could also be really handy for tracking stats of users... Nyall --strk; ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Freeze on release-2_8 branch
On 14 July 2015 at 00:04, Matthias Kuhn matth...@opengis.ch wrote: Hi On Mon, Jul 13, 2015 at 03:44:28PM +0200, Sandro Santilli wrote: On Mon, Jul 13, 2015 at 03:30:38PM +0200, Matthias Kuhn wrote: Regarding this, I would propose to put the freeze in place as of Tue, Jul 14, 12:00 UTC And - presuming there are no regressions found - 2.8.3 will be tagged on Tue, Jul, 28. +1, but I'd avoid the word freeze as it may be confusing. We're basically asking all developers to refrain from pushing more backports in that branch until 2.8.3 is released. Oh, forgot to mention, we're also asking developers to _test_ the branch, or it would make no sense to wait another week, right ? It might actually help to make an official call for testing on the users list too. I'm sure many will be happy to test the next stable release before it comes out (either from snapshot or directly from git). I've submitted by make Experimental already. --strk; +1 I planned to send a tweet tomorrow but any widespread call for testing will be good (but mainly by power users and organizations who actually use it. We cannot put that also on the developers back) I'd really like to backport c8dcf97 (critical for 2.8.3 IMO) and a1a8d1b (nice to have for 2.8.3), but don't want to reset the countdown now. Is there anyway around this? Nyall ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Freeze on release-2_8 branch
Hi Jürgen On 07/13/2015 01:23 PM, Jürgen E. Fischer wrote: Hi Matthias, On Mon, 13. Jul 2015 at 12:46:50 +0200, Matthias Kuhn wrote: I think it would be great to branch a release-candidate-2_8_3 (no binaries released, just to backport possible issues identified on the release-2_8 binaries, related to pre-rc-commits). This way people can happily continue to backport stuff. What's the point if there are no binaries? Testing is done not intensive enough even with binaries - w/o binaries it's likely to be even worse. That our release manager does not need to create yet another set of binaries. And I am confident, that a bug introduced with a pre-release-candidate commit will also be identified on the binaries produced for the release-branch with a couple of unrelated commits on top. Until this happens (and mainly for the situation where it does not happen) *I would like to ask all committers to stop backporting to the release-2_8 branch* as of tomorrow, July 14, 2015 (so you have still today to push the urgent fixes you never got round to merge). This way we'll have a stable 2.8.3 in the beginning of August. That's can be done without a separate branch - and w/o a separate branch there would be nightlies to test... That's why I proposed that one in bold :) My concern is more when https://github.com/qgis/QGIS/pull/2197 is going to be resolved - as that is what 2.10.1 is waiting for. There are still 24 hours to merge it and follow the proposed schedule. Best, Matthias signature.asc Description: OpenPGP digital signature ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Freeze on release-2_8 branch
Hi Matthias, On Mon, 13. Jul 2015 at 13:44:49 +0200, Matthias Kuhn wrote: On 07/13/2015 01:23 PM, Jürgen E. Fischer wrote: On Mon, 13. Jul 2015 at 12:46:50 +0200, Matthias Kuhn wrote: I think it would be great to branch a release-candidate-2_8_3 (no binaries released, just to backport possible issues identified on the release-2_8 binaries, related to pre-rc-commits). This way people can happily continue to backport stuff. What's the point if there are no binaries? Testing is done not intensive enough even with binaries - w/o binaries it's likely to be even worse. That our release manager does not need to create yet another set of binaries. And I am confident, that a bug introduced with a pre-release-candidate commit will also be identified on the binaries produced for the release-branch with a couple of unrelated commits on top. Until this happens (and mainly for the situation where it does not happen) *I would like to ask all committers to stop backporting to the release-2_8 branch* as of tomorrow, July 14, 2015 (so you have still today to push the urgent fixes you never got round to merge). This way we'll have a stable 2.8.3 in the beginning of August. That's can be done without a separate branch - and w/o a separate branch there would be nightlies to test... That's why I proposed that one in bold :) I still don't get the purpose of the release-candidate-2_8_3 branch. I'd say we declare a backport freeze now and only apply stuff introduced by backports in release-2_8 until we do a point release after two weeks. After that backporting can continue. My concern is more when https://github.com/qgis/QGIS/pull/2197 is going to be resolved - as that is what 2.10.1 is waiting for. There are still 24 hours to merge it and follow the proposed schedule. Jürgen -- Jürgen E. Fischer norBIT GmbH Tel. +49-4931-918175-31 Dipl.-Inf. (FH) Rheinstraße 13 Fax. +49-4931-918175-50 Software Engineer D-26506 Norden http://www.norbit.de QGIS release manager (PSC) GermanyIRC: jef on FreeNode signature.asc Description: Digital signature ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Freeze on release-2_8 branch
Hi On 07/13/2015 02:27 PM, Jürgen E. Fischer wrote: Until this happens (and mainly for the situation where it does not happen) *I would like to ask all committers to stop backporting to the release-2_8 branch* as of tomorrow, July 14, 2015 (so you have still today to push the urgent fixes you never got round to merge). This way we'll have a stable 2.8.3 in the beginning of August. That's can be done without a separate branch - and w/o a separate branch there would be nightlies to test... That's why I proposed that one in bold :) I still don't get the purpose of the release-candidate-2_8_3 branch. If somebody discovers a commit which is worth backporting tomorrow he can do so without postponing 2.8.3 and without the risk of forgetting what he wanted to backport until the freeze is over. I'd say we declare a backport freeze now and only apply stuff introduced by backports in release-2_8 until we do a point release after two weeks. After that backporting can continue. Fair enough, no big deal. And (accidental) backports during this time get reverted? Any opinion concerning 2197? Will a deadline in 24h be good enough? Matthias signature.asc Description: OpenPGP digital signature ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Freeze on release-2_8 branch
Hi Matthias, On Mon, 13. Jul 2015 at 12:46:50 +0200, Matthias Kuhn wrote: I think it would be great to branch a release-candidate-2_8_3 (no binaries released, just to backport possible issues identified on the release-2_8 binaries, related to pre-rc-commits). This way people can happily continue to backport stuff. What's the point if there are no binaries? Testing is done not intensive enough even with binaries - w/o binaries it's likely to be even worse. Until this happens (and mainly for the situation where it does not happen) *I would like to ask all committers to stop backporting to the release-2_8 branch* as of tomorrow, July 14, 2015 (so you have still today to push the urgent fixes you never got round to merge). This way we'll have a stable 2.8.3 in the beginning of August. That's can be done without a separate branch - and w/o a separate branch there would be nightlies to test... My concern is more when https://github.com/qgis/QGIS/pull/2197 is going to be resolved - as that is what 2.10.1 is waiting for. Jürgen -- Jürgen E. Fischer norBIT GmbH Tel. +49-4931-918175-31 Dipl.-Inf. (FH) Rheinstraße 13 Fax. +49-4931-918175-50 Software Engineer D-26506 Norden http://www.norbit.de QGIS release manager (PSC) GermanyIRC: jef on FreeNode signature.asc Description: Digital signature ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Freeze on release-2_8 branch
On Mon, Jul 13, 2015 at 02:36:22PM +0200, Matthias Kuhn wrote: On 07/13/2015 02:27 PM, Jürgen E. Fischer wrote: I still don't get the purpose of the release-candidate-2_8_3 branch. If somebody discovers a commit which is worth backporting tomorrow he can do so without postponing 2.8.3 and without the risk of forgetting what he wanted to backport until the freeze is over. Pull requests can still be opened against the 2.8 branch, to avoid the risk of forgetting (and at the same time to have travis also keep an eye on the outcome). --strk; ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Freeze on release-2_8 branch
On Mon, Jul 13, 2015 at 03:30:38PM +0200, Matthias Kuhn wrote: The general opinion seems to point towards freeze and not branch. Regarding this, I would propose to put the freeze in place as of Tue, Jul 14, 12:00 UTC And - presuming there are no regressions found - 2.8.3 will be tagged on Tue, Jul, 28. +1, but I'd avoid the word freeze as it may be confusing. We're basically asking all developers to refrain from pushing more backports in that branch until 2.8.3 is released. I guess the regression exception should be better defined, how about just requesting that any commit to the branch should be first discussed on the mailing list, after it was prepared as a pull request against the 2.8 branch ? --strk; () Free GIS Flash consultant/developer /\ http://strk.keybit.net/services.html ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Freeze on release-2_8 branch
On Mon, Jul 13, 2015 at 03:44:28PM +0200, Sandro Santilli wrote: On Mon, Jul 13, 2015 at 03:30:38PM +0200, Matthias Kuhn wrote: Regarding this, I would propose to put the freeze in place as of Tue, Jul 14, 12:00 UTC And - presuming there are no regressions found - 2.8.3 will be tagged on Tue, Jul, 28. +1, but I'd avoid the word freeze as it may be confusing. We're basically asking all developers to refrain from pushing more backports in that branch until 2.8.3 is released. Oh, forgot to mention, we're also asking developers to _test_ the branch, or it would make no sense to wait another week, right ? It might actually help to make an official call for testing on the users list too. I'm sure many will be happy to test the next stable release before it comes out (either from snapshot or directly from git). I've submitted by make Experimental already. --strk; ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Freeze on release-2_8 branch
Hi Matthias, On Mon, 13. Jul 2015 at 14:36:22 +0200, Matthias Kuhn wrote: Fair enough, no big deal. And (accidental) backports during this time get reverted? Any opinion concerning 2197? Will a deadline in 24h be good enough? 2197 doesn't apply to 2.8. Jürgen -- Jürgen E. Fischer norBIT GmbH Tel. +49-4931-918175-31 Dipl.-Inf. (FH) Rheinstraße 13 Fax. +49-4931-918175-50 Software Engineer D-26506 Norden http://www.norbit.de QGIS release manager (PSC) GermanyIRC: jef on FreeNode signature.asc Description: Digital signature ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Freeze on release-2_8 branch
The general opinion seems to point towards freeze and not branch. Regarding this, I would propose to put the freeze in place as of Tue, Jul 14, 12:00 UTC And - presuming there are no regressions found - 2.8.3 will be tagged on Tue, Jul, 28. Kind regards, Matthias ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Freeze on release-2_8 branch
Hi On Mon, Jul 13, 2015 at 03:44:28PM +0200, Sandro Santilli wrote: On Mon, Jul 13, 2015 at 03:30:38PM +0200, Matthias Kuhn wrote: Regarding this, I would propose to put the freeze in place as of Tue, Jul 14, 12:00 UTC And - presuming there are no regressions found - 2.8.3 will be tagged on Tue, Jul, 28. +1, but I'd avoid the word freeze as it may be confusing. We're basically asking all developers to refrain from pushing more backports in that branch until 2.8.3 is released. Oh, forgot to mention, we're also asking developers to _test_ the branch, or it would make no sense to wait another week, right ? It might actually help to make an official call for testing on the users list too. I'm sure many will be happy to test the next stable release before it comes out (either from snapshot or directly from git). I've submitted by make Experimental already. --strk; +1 I planned to send a tweet tomorrow but any widespread call for testing will be good (but mainly by power users and organizations who actually use it. We cannot put that also on the developers back) Matthias signature.asc Description: OpenPGP digital signature ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
