Time for new release?

[nilason]

A neat change log has accumulated since the 1.0.2 release: 1.0.2...main
Perhaps the biggest change is the added support of CMake.
Maybe it is time for a new release: 1.0.3?

There is a pending pull request #37, which I'm not sure if it should go to a patch release or rather to 1.1.0?

A future 1.1.0 release could possibly also be a the first release with CMake only (ie. dropping Autotools configure) – to simplify maintenance. If this proposition is agreed upon, I'd suggest we deprecate Autotools configure with the 1.0.3 release and then create a 1.0 release branch.

[neteler]

I am in favor of a new release.

Perhaps we could borrow the https://github.com/OSGeo/grass/blob/main/utils/generate_release_notes.py script to simplify the ChangeLog creation with due author credit entries etc.?

[neteler]

So, suggestion for the roadmap:

Create the upcoming version 1.0.3 release:

• deprecate Autotools configure with the 1.0.3 release
• and https://github.com/OSGeo/gdal-grass/milestone/4?closed=1

Then create a 1.0 release branch.

Create the upcoming version 1.1.0 release:

• drop Autotools configure
• merge Modernise C++ code #37
• first release with CMake only

[nilason]

Sounds good to me!

[neteler]

Silly question: "deprecate Autotools configure with the 1.0.3 release" - simply by communicating it in the release notes or by doing more?

[nilason]

Silly question: "deprecate Autotools configure with the 1.0.3 release" - simply by communicating it in the release notes or by doing more?

Yes, I think that is what we can do, and encourage building/installation using cmake.

[neteler]

Silly question: "deprecate Autotools configure with the 1.0.3 release" - simply by communicating it in the release notes or by doing more?

Addressed in #43

[schwehr]

Bringing info over from my duplicate issue...

Now that the CPL_CVSID() macro was removed in #50, it would great to have a new release of gdal-grass. This will support work in GDAL to remove that macro. See OSGeo/gdal#11433

[nilason]

#44 is now merged, I believe we're ready for a release.

[neteler]

I'm traveling much of this week, feel free to go for the release, @nilason.

[nilason]

I'm traveling much of this week, feel free to go for the release, @nilason.

Good, I will! I'd suggest we start with a RC1, in particular considering the new cmake code.
We should, however, hold on the announcement till you have the opportunity to transfer the tarball(s) to OSGeo server.