[QGIS-Developer] QGIS 4.0 - let's start some early discussions!

[Tim Sutton]

Hi



> On 25 Jun 2019, at 12:27, Nathan Woodrow <madmanwoo at gmail.com> wrote:
> 
> Personally, I'm a bit uncomfortable with any kind of API break if we can avoid it which means we don't need to call it 4.0 as that marks a major API break when bumping that version number?  Any reason we need to make it 4.0 and not just continue down the 3.x stream until we are forced to break APIS?
> 
> We should be able to migrate away from any API breaks in theory right? We couldn't for 3.0 because of all the SIP and Python 3 stuff but that shouldn't be the case in Qt 6 hopefully.
> 
> That is just my take.  We need to maintain a stable API for as long as possible if we can which I know you know I'm just double voicing it.
> 

If the Qt6 is broken (even gently :-P) and we plan to base QGIS 4 on it then even if our stuff is API compatible, the surrounding things that plugin authors have used may be broken, which would for me still justify calling it 4.0 instead of 3.x. 

Regards

Tim

> - Nathan
> 
> On Tue, Jun 25, 2019 at 7:42 PM Nyall Dawson <nyall.dawson at gmail.com <mailto:nyall.dawson at gmail.com>> wrote:
> Hi all,
> 
> Following conversation from https://github.com/qgis/QGIS/pull/30234 <https://github.com/qgis/QGIS/pull/30234>, I
> think it would be beneficial if we start the conversation happening
> about QGIS 4.0, and to throw some thoughts about timelines out there.
> 
> **Before anyone panics -- I'm expecting multi-year time frames here!
> But I think we should START this discussion, and have at least some
> idea of the time frames we're all aiming toward for a future 4.0
> release.**
> 
> For reference: Qt upstream has previously hinted at November 2020 for
> Qt 6, at which stage support for 5.x will be dropped. Discussions so
> far are moving toward Qt 6 being a "gentle" cleaning, so there's
> likely (hopefully?) not a lot we'll be forced to do to adapt to this.
> 
> I think we should aim for a similar goal -- a "gentle" API break, as
> opposed to the huge-clean-and-break-everything-we-possibly-can
> approach we took for 3.x (with good reason!).
> 
> Thoughts?
> 
> Nyall
> _______________________________________________
> QGIS-Developer mailing list
> QGIS-Developer at lists.osgeo.org <mailto:QGIS-Developer at lists.osgeo.org>
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer <https://lists.osgeo.org/mailman/listinfo/qgis-developer>
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer <https://lists.osgeo.org/mailman/listinfo/qgis-developer>_______________________________________________
> QGIS-Developer mailing list
> QGIS-Developer at lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

—









Tim Sutton

Co-founder: Kartoza
Ex Project chair: QGIS.org

Visit http://kartoza.com <http://kartoza.com/> to find out about open source:

Desktop GIS programming services
Geospatial web development
GIS Training
Consulting Services

Skype: timlinux 
IRC: timlinux on #qgis at freenode.net

I'd love to connect. Here's my calendar link <https://calendly.com/timlinux> to make finding time easy.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/qgis-developer/attachments/20190625/fe0f6b78/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: KartozaNewLogoThumbnail.jpg
Type: image/jpeg
Size: 6122 bytes
Desc: not available
URL: <http://lists.osgeo.org/pipermail/qgis-developer/attachments/20190625/fe0f6b78/attachment-0001.jpg>