Is it time for a 0.29.0 release?

[kevinbackhouse]

Is it time to create a 0.29.x branch and a prepare a 0.29.0 release?

I think the 0.28.x branch was created in 2023:

git merge-base Exiv2/0.28.x Exiv2/main: c86ae6acf597304db37246434ebc393d732c22c2

A lot of the discussion about starting the 0.28 series happened here: #2406

[jim-easterbrook]

Are there any API changes to justify a new series?

[kevinbackhouse]

Are there any API changes to justify a new series?

I suspect so. There are quite a few changes in the include directory:

git diff Exiv2/0.28.x Exiv2/main include

Also, we dropped support for C++11 and switched to C++20 by default.

@neheb will know more.

[kmilos]

I don't feel there is a major pull for the C++20 switch just yet like there was for C++17 around 0.28.x time, so I'm ok w/ waiting until a late moment (e.g. next spring?) - less backporting overhead that way...

[jim-easterbrook]

Are there any API changes to justify a new series?

I suspect so. There are quite a few changes in the include directory:

git diff Exiv2/0.28.x Exiv2/main include

Ah! You mean a new branch from main. (I still think of main as the 1.0.0 branch.) I've not been keeping up with developments there.

[kevinbackhouse]

Ah! You mean a new branch from main. (I still think of main as the 1.0.0 branch.) I've not been keeping up with developments there.

That's right, I mean a new branch from main.

[neheb]

Maybe if some significant API change gets introduced.

The dropping of C++11 from the headers is just a result of the current compiler landscape. It's not significant.

Same with C++20.