On 4/25/21 7:03 AM, Lassi Kortela wrote:

> Oh, and the yearly stable releases (suggested for Scheme Live) would
> still be a good idea IMHO. So any code/spec can change at any time,
> but once a year, we cut a stable release of the interface at that
> point. People who are interested in long term stability can continue
> to maintain implementation(s) of that interface. That would really be
> the only formal thing needed.

There are a few possible approaches to stability. Yearly stable releases
is one of them, but that's still moving very slowly. Another possible
approach is something like Semantic Versioning: have rules about when
the version of each module changes, and include that version in the
module name.

So instead of something like (scheme-live string) you'd have
(scheme-live string 1), and then if someone made a breaking change to
the API (removed or renamed a procedure, changed the number of arguments
to a procedure, etc.), the new change would have to be (scheme-live
string 2), and the old version would still exist. Then updates won't
break existing code.