<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On 4. Jun 2023, at 15:03, Urs Fleisch <<a href="mailto:urs.fleisch@gmail.com" class="">urs.fleisch@gmail.com</a>> wrote:</div><div class=""><div dir="ltr" class=""><br class=""> * Reduce risks by carefully continuing on the master branch and not switch<br class=""> to the taglib2 branch (see also discussion at the end of<br class=""> <a href="https://github.com/taglib/taglib/issues/837" class="">https://github.com/taglib/taglib/issues/837</a>).</div></div></blockquote><br class=""></div><div>The plan in general makes total sense to me — a couple things I’d suggest in that push:</div><div><br class=""></div><div>- 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?)</div><div>- Renaming the taglib2 branch to “experimental” or something to avoid the current confusion.</div><div><br class=""></div><div>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.</div><div><br class=""></div><div>-Scott</div></body></html>