<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 22. Jun 2023, at 16:02, Fred Gleason <<a href="mailto:fredg@paravelsystems.com" class="">fredg@paravelsystems.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html; charset=utf-8" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">On Jun 22, 2023, at 04:30, Scott Wheeler <<a href="mailto:scott@taglib.org" class="">scott@taglib.org</a>> wrote:<div class=""><br class=""><div class=""><blockquote type="cite" class=""><div class=""><div style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;" class="">- 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 style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;" class="">- Renaming the taglib2 branch to “experimental” or something to avoid the current confusion.</div></div></blockquote><br class=""></div><div class="">Am I to understand from this that an ABI update is in prospect here? I’ve had things on my wish list for taglib (support for EBU 3285 and AES46) for years that I’ve never really pushed on because of the situation with being locked into the KDE ABI. If in fact a window for such changes is opening, I’d be very interested in helping to make such support happen.</div></div></div></div></blockquote><br class=""></div><div>I don’t know anything about either of those formats, but why would they need an ABI break? Lots of new formats have been added in the 20 years that TagLib’s had ABI stability.</div><div><br class=""></div><div>TagLib’s never been bound by KDE’s ABI policies; it’s just been easy enough to keep the ABI working, so we have. </div><div><br class=""></div><div>(It’d be kind of funny to release on January 24, 2024, exactly 20 years after 1.0.)</div><div><br class=""></div><div>-Scott</div><br class=""></body></html>