[Qgis-developer] QEP - Proposal for QGIS 3.0 after 2.14

[Nathan Woodrow]

Of course we can develop it without breaking anything if done in a branch.
But having a plan around all this is the point of all this I think just so
we are all on the same page

On Sun, 25 Oct 2015 5:11 pm Matthias Kuhn <matthias at opengis.ch> wrote:

>
> On 10/24/2015 09:13 PM, Nyall Dawson wrote:
> >
> > But keeping the possibility of merging the branch before 2.14 means
> > the api is locked... That's not ideal, it'll create a lot of
> > (unneeded) extra work. I'd say allow breaks in the branch, merge after
> > 2.14.
> >
>
> Why does that mean that the API is locked?
>
>
> On 10/25/2015 12:42 AM, Nathan Woodrow wrote:
> >
> > What ever we do we just can't break plugins unless it's planned out
> > and all in one go to reduce the number of updates that need to be done
> >
> >
>
> Introduction of code to support python 3 and pyqt5 does not break
> plugins if done right.
>
> It only may break plugins if it's turned on. Therefore it's not the work
> on this code that should be concerted but the deployment of binaries
> with support for these features.
>
>
>
> _______________________________________________
> Qgis-developer mailing list
> Qgis-developer at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/qgis-developer
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/qgis-developer/attachments/20151025/48ff2d17/attachment-0001.html>