Can you two be more specific about the API breakages? I've quickly looked at `git log --oneline 3.0.0..3.1.0` and couldn't to figure out based on that what you are talking about. And the CHANGES stops at 3.0.0.
FWIW: agreed that stability is a relative concept. What would be useful, though, is clarifying publicly in the doc whether Beancount adheres to something like Semantic Versioning or not. (Yes, semver is not a panacea either, but it's becoming a common reference for developer expectations on this kind of stuff.) Cheers On Mon, Jan 20, 2025 at 08:27:24AM -0500, Martin Blais wrote: > Wait, can't you just pin beangulp to 3.0.x using a lockfile? > If we switch to versions (vs. always-at-head development), I believe you > have to do that. > > Stability is a relative concept; I don't think I've ever stated a specific > version-related stability guarantee. > (You're assuming minor version stable on the API front.) -- Stefano Zacchiroli . [email protected] . https://upsilon.cc/zack _. ^ ._ Full professor of Computer Science o o o \/|V|\/ Télécom Paris, Polytechnic Institute of Paris o o o </> <\> Co-founder & CSO Software Heritage o o o o /\|^|/\ Mastodon: https://mastodon.xyz/@zacchiro '" V "' -- You received this message because you are subscribed to the Google Groups "Beancount" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/d/msgid/beancount/20250120133604.emnk652rwxucool6%40upsilon.cc.
