[PROJ] Release schedule

[Kristian Evers]

No objections, as it were. This will be the release schedule for the next couple of years.
I’ve added the releases up til 8.0.0 as milestones on GitHub:

https://github.com/OSGeo/PROJ/milestones?direction=asc&sort=due_date&state=open

I’m sure circumstances will warrant changes to the schedule. I expect that a bugfix
release migt be changed to a new-feature release at some point. I intend to stick with
the bimonthly schedule though.

I have only put in one milestone for the 6.x branch but there may be more than one
release of that branch if it isn’t too complicated to backport fixes. Basically I don’t want
promise anything but we’ll try to keep it going as long as possible.

/Kristian

On 26 Feb 2020, at 15:55, Kristian Evers <kreve at sdfe.dk<mailto:kreve at sdfe.dk>> wrote:

All,

With the release of PROJ 7 we are out of scheduled releases. I want to put in place a new schedule so that downstream projects can plan their own releases accordingly. Lately we've seen a few interconnected bugs in QGIS where an unfortunate combination of new PROJ and GDAL was used in a QGIS version build for an older combination of PROJ/GDAL. This was no-ones fault but could have been avoided with a bit of planning across the projects. This is a step in that direction.

I propose we continue the release frequency that was used between 6.0.0 and 7.0.0. That is, bimonthly releases alternating between bug fix releases (patch) and new-feature releases (minor version number) culminating in a major release version in March. Of course with the option of promoting a bug fix release to a minor version release if that is deemed preferable. Ad hoc releases like 6.3.1 will also be a possibility but only for bug fixes and shouldn't mess up the overall schedule.

I've looked into other OSGeo projects release schedules but unfortunately it seems to be only QGIS that has a long-term plan for their releases [0]. I haven't been able to find the same for projects like GDAL, PostGIS, Mapserver, etc.

Below I have made a list of up-coming my proposed PROJ release and intertwined them with planned (or presumed [1]) QGIS releases in the future:

PROJ 6.3.1:  2020-02-13
QGIS 3.12.0: 2020-02-21
PROJ 7.0.0:  2020-03-01
PROJ 7.0.1:  2020-05-01
QGIS 3.14.0: 2020-06-19
PROJ 7.1.0:  2020-07-01
PROJ 7.1.1:  2020-09-01
QGIS 3.16.0: 2020-10-23 (LTR)
PROJ 7.2.0:  2020-11-01
PROJ 7.2.1:  2021-01-01
QGIS 3.18.0: 2021-02-xx
PROJ 8.0.0:  2021-03-01
PROJ 8.0.1:  2021-05-01
QGIS 3.20.0: 2021-06-xx
PROJ 8.1.0:  2021-07-01
PROJ 8.1.1:  2021-09-01
QGIS 3.22.0: 2021-10-xx (LTR)
PROJ 8.2.0:  2021-11-01
PROJ 8.2.1:  2022-01-01
PROJ 8.3.0:  2022-03-01

As it can be seen from the list the two schedules generally fit well together with QGIS long-term releases being issued roughly two months after PROJ as had the fix bug fix release of a new minor version branch. Or put in another way, we've had four releases to weed out bugs in a new major version release, which should provide a solid release for QGIS to build on.

I tried to look up the release schedules of various Linux distributions to see how those would fit since in the end the packaging systems will be the limiting factor for the whole OSGeo stack. I found it hard to come to any form of conclusion that could guide our release schedule though. I assume most distributions will be a major version branch behind when it comes to PROJ for the next year or two, until we have weeded out proj_api.h for good.

It would be great to get feedback on the release schedule from PROJ developers, developers of other packages depending on PROJ and the packagers as well.

/Kristian

[0] https://www.qgis.org/en/site/getinvolved/development/roadmap.html
[1] QGIS release dates ending in xx are presumed releases that doesn't figure in the road map

_______________________________________________
PROJ mailing list
PROJ at lists.osgeo.org<mailto:PROJ at lists.osgeo.org>
https://lists.osgeo.org/mailman/listinfo/proj

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/proj/attachments/20200303/5c4f8155/attachment-0001.html>