Re: [Qgis-developer] Extending timeline for 3.0?
Hi Nyall, On Wed, 26. Oct 2016 at 17:09:29 +1000, Nyall Dawson wrote: > "oh but we had already planned our corporate deployment schedule > around a March release!!11!!". Better to openly discuss this > possibility so everyone's on the same page. If we are all on the http://www.qgis.org/en/site/getinvolved/development/roadmap.html#release-schedule page - it estimates 8-12 months from the release of 2.16 - so that would be March to July '17. 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 pgpMfEKP5WOv3.pgp Description: PGP signature ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Extending timeline for 3.0?
Il 26/10/2016 09:09, Nyall Dawson ha scritto: > I realise that - but March has been thrown around tentatively. I'd > hate to get to February and then have this blocked by responses like > "oh but we had already planned our corporate deployment schedule > around a March release!!11!!". Better to openly discuss this > possibility so everyone's on the same page. Thanks Nyall for raising this. I think this is quite reasonable. The main issue I see is with people sponsoring new features not being able to use it before next summer. Probably they will put pressure for releasing a new version, or for making an exception to the no-new-feature rule. How could we cope with that? All the best. -- Paolo Cavallini - www.faunalia.eu QGIS & PostGIS courses: http://www.faunalia.eu/training.html https://www.google.com/trends/explore?date=all=IT=qgis,arcgis ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Extending timeline for 3.0?
On 26 October 2016 at 16:22, Jürgen E. Fischerwrote: > Hi Nyall, > > On Wed, 26. Oct 2016 at 15:53:22 +1000, Nyall Dawson wrote: >> What are everyone's thoughts on extending the timeline for 3.0? > > What timeline is there to extend? We didn't set a date - just had rough > ideas. I realise that - but March has been thrown around tentatively. I'd hate to get to February and then have this blocked by responses like "oh but we had already planned our corporate deployment schedule around a March release!!11!!". Better to openly discuss this possibility so everyone's on the same page. Nyall > > > 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 > > ___ > Qgis-developer mailing list > Qgis-developer@lists.osgeo.org > List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer > Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Extending timeline for 3.0?
Hi Nyall, On Wed, 26. Oct 2016 at 15:53:22 +1000, Nyall Dawson wrote: > What are everyone's thoughts on extending the timeline for 3.0? What timeline is there to extend? We didn't set a date - just had rough ideas. 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 pgpxIb4U7sWiK.pgp Description: PGP signature ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Extending timeline for 3.0?
Hi, I agree with Nyall. As this is a major release this requires more time, have a look at how long it took Python 3 to finally become used for an idea on how people treat major breaks in API. As we already have 2.14, 1.6 and 2.18 out the door as a really good base I don't see a need to rush this out. I have plans for 3.0 but don't have a Windows build setup yet. Regards, Nathan On Wed, Oct 26, 2016 at 4:10 PM, Neumann, Andreaswrote: > Hi, > > It would be fine for me to have a double dev cycle for 3.0. Devs should > have enough time to make proper decisions and work on the API. And python > devs probably also need more time to get their most important plugins in > shape for the new API, qt5 and Python 3. > > Perhaps it would be good to also have more than one month for testing and > bug fixing - extending this to two months. We could simply shift the one > month bug fixing/testing of the first cycle towards the end of the second > cycle. > > So this modified proposal would mean: > > Feature freeze at the end of May, release at the end of July. Right? > > Fine with me, if we still care about the 2.x branch where necessary - > preferably investing more in 2.18x than in 2.14x (my personal opinion). > > Andreas > > On 2016-10-26 07:53, Nyall Dawson wrote: > > Hi all, > > I'd like to start the discussion around this early so that we can plan > ahead and not have to make a last-minute decision. > > What are everyone's thoughts on extending the timeline for 3.0? In my > opinion things are currently going really well, we have Qt5/python3 > builds which are stable enough for daily use and there's been a ton of > cleanups to the code. > > There's a lot of changes still coming in, and I think there's SO much > room for making things better that I don't like the idea of the early > 2017 deadline for the final release. I'd much rather extend this out > by another cycle and really getting the platform ready for the next > series of QGIS releases. > > We could always put out a "preview" release in March, without frozen > API, if desired. > > So, what's everyone's thoughts? Good idea? Bad idea? > > Nyall > ___ > Qgis-developer mailing list > Qgis-developer@lists.osgeo.org > List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer > Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer > > > > > ___ > Qgis-developer mailing list > Qgis-developer@lists.osgeo.org > List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer > Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer > ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Extending timeline for 3.0?
Hi, It would be fine for me to have a double dev cycle for 3.0. Devs should have enough time to make proper decisions and work on the API. And python devs probably also need more time to get their most important plugins in shape for the new API, qt5 and Python 3. Perhaps it would be good to also have more than one month for testing and bug fixing - extending this to two months. We could simply shift the one month bug fixing/testing of the first cycle towards the end of the second cycle. So this modified proposal would mean: Feature freeze at the end of May, release at the end of July. Right? Fine with me, if we still care about the 2.x branch where necessary - preferably investing more in 2.18x than in 2.14x (my personal opinion). Andreas On 2016-10-26 07:53, Nyall Dawson wrote: > Hi all, > > I'd like to start the discussion around this early so that we can plan > ahead and not have to make a last-minute decision. > > What are everyone's thoughts on extending the timeline for 3.0? In my > opinion things are currently going really well, we have Qt5/python3 > builds which are stable enough for daily use and there's been a ton of > cleanups to the code. > > There's a lot of changes still coming in, and I think there's SO much > room for making things better that I don't like the idea of the early > 2017 deadline for the final release. I'd much rather extend this out > by another cycle and really getting the platform ready for the next > series of QGIS releases. > > We could always put out a "preview" release in March, without frozen > API, if desired. > > So, what's everyone's thoughts? Good idea? Bad idea? > > Nyall > ___ > Qgis-developer mailing list > Qgis-developer@lists.osgeo.org > List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer > Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer
[Qgis-developer] Extending timeline for 3.0?
Hi all, I'd like to start the discussion around this early so that we can plan ahead and not have to make a last-minute decision. What are everyone's thoughts on extending the timeline for 3.0? In my opinion things are currently going really well, we have Qt5/python3 builds which are stable enough for daily use and there's been a ton of cleanups to the code. There's a lot of changes still coming in, and I think there's SO much room for making things better that I don't like the idea of the early 2017 deadline for the final release. I'd much rather extend this out by another cycle and really getting the platform ready for the next series of QGIS releases. We could always put out a "preview" release in March, without frozen API, if desired. So, what's everyone's thoughts? Good idea? Bad idea? Nyall ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer