Re: [Qgis-developer] Status of Q3 migration?

2016-12-06 10:47 GMT+01:00 Paolo Cavallini : > Il 06/12/2016 09:20, Régis Haubourg ha scritto: > > > @Paolo, I think we are not yet in polishing step, some really low level > > things still need to be broken and rebuilt. See > > there:

Re: [Qgis-developer] Status of Q3 migration?

* -1 for QGIS development to go back to the "wait until ready" mode which delayed QGIS 2.0 way too long * +0.5 to have a serious discussion around a possible (fixed in time) extension :) Let's not forget that while of us on the dev mailing list run on home-made or nightly builds, which tents to

Re: [Qgis-developer] Status of Q3 migration?

Hi all, I propose I add this as a discussion topic at the end of the Lyon Code Sprint next week. We'll maybe have a clearer view of how much work is remaining. @Paolo, I think we are not yet in polishing step, some really low level things still need to be broken and rebuilt. See there:

Re: [Qgis-developer] Status of Q3 migration?

Hi, I would also prefer a double dev cycle, followed by a double test period. So just shift the one month from the first dev cycle towards the end. In Bonn we discussed this and I think the double dev cycle was an option, but we said we would decide in December/January when we know more about

Re: [Qgis-developer] Status of Q3 migration?

Hi all, Il 06/12/2016 00:02, Nyall Dawson ha scritto: > Hmm I've brought up previously on the list my thoughts that we > should *extend* the timeline to mid next year, as opposed to speeding > it up. > > See https://lists.osgeo.org/pipermail/qgis-developer/2016-October/045554.html > > I'm

Re: [Qgis-developer] Status of Q3 migration?

On 3 December 2016 at 19:51, Paolo Cavallini wrote: > Hi all, > I'm regularly compiling QGIS master, and I'm surprised how usable and > smooth it is - obviously not suitable for production, but apparently not > so far from it. It would be great if those more involved with

[Qgis-developer] Status of Q3 migration?

Hi all, I'm regularly compiling QGIS master, and I'm surprised how usable and smooth it is - obviously not suitable for production, but apparently not so far from it. It would be great if those more involved with the migration could give us a quick overview: * are there blocking factors? * which