Hello, Andy Wingo <wi...@pobox.com> skribis:
> On Tue 23 Jun 2020 11:36, Chris Vine <vine35792...@gmail.com> writes: [...] >>> I was hesitant about the SONAME: the ABI jump was unnecessary unless in >>> ‘--disable-deprecated’ builds. I erred on the side of cautiousness: >>> >>> >>> https://git.savannah.gnu.org/cgit/guile.git/commit/?id=5d052c87bd8f0fd894e67f0bebd4fa6f6160d83c >> >> Hi, >> >> Ah right. There must have been two SO breaks between guile-3.0.2 and >> guile-3.0.3. >> >> It's a nuisance having SO bumps on micro releases and I wonder if that >> could be included in the announcement so that you don't first notice it >> when stuff fails to run? > > I think I agree with Chris. The intention is certainly to have a stable > ABI within a stable series, so 3.0.3 should have the same CURRENT. > > It's certainly correct that a --disable-deprecated 3.0.3 build has a > different ABI than 3.0.2, and if that were what we were looking at, we > would indeed need the CURRENT version bump; but I think the premise is > wrong: we do *not* have a stable ABI in --disable-deprecated builds, and > we never have. Otherwise we wouldn't ever be able to deprecate anything > within a stable series. Following our discussion on IRC, I agree with restoring CURRENT and will push a 3.0.4 in that direction. Apologies for the annoyance! Ludo’.
