Hi,
There's already a wishlist of what could be done there:
https://github.com/qgis/qgis4.0_api/issues
Maybe you can add your ideas to this list, Raymond (and others).
I am also in favor of waiting at least 2+ more years before doing a
major upgrade to give users some investment security when migrating and
deploying their systems.
And with a good communication about a "gentle" break I'm confident that
we'll have it easier this time.
Furthermore, it would be nice to go over this list of issues and see
what we can actually already can make happen before and deprecate, so
pyqgis devs can even have a smoother experience by being able to develop
against a future API even before. (Thinking about
https://github.com/qgis/qgis4.0_api/issues/90 and smilar here)
Regards
Matthias
On 6/25/19 1:37 PM, Raymond Nijssen wrote:
Not sure about the changes in QT 6 but I think if the API breaks we
should call it QGIS 4.
And when the API breaks anyway, I would love to have the geometry
model improved and am willing to help.
Raymond
On 25-06-19 11:41, Nyall Dawson wrote:
Hi all,
Following conversation from 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
[email protected]
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
_______________________________________________
QGIS-Developer mailing list
[email protected]
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
_______________________________________________
QGIS-Developer mailing list
[email protected]
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
