Next release

[Scott Wheeler]

> On 4. Jun 2023, at 15:03, Urs Fleisch <urs.fleisch at gmail.com> wrote:
> 
>  * Reduce risks by carefully continuing on the master branch and not switch
>    to the taglib2 branch (see also discussion at the end of
>    https://github.com/taglib/taglib/issues/837 <https://github.com/taglib/taglib/issues/837>).

The plan in general makes total sense to me — a couple things I’d suggest in that push:

- Mining the taglib2 branch for API changes that we might want to consider before another potentially decades long ABI freeze.  (Basically using it as a sanity check:  are there any virtual functions that need to added?)
- Renaming the taglib2 branch to “experimental” or something to avoid the current confusion.

To be honest, “experimental” would probably have always been a better label for it, since it was a branch that never had a release strategy or imagined timeline.

-Scott
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/taglib-devel/attachments/20230622/cf7ff8bb/attachment.htm>