What's the current new package system policy on non-backward-compatible
changes in a package version?
I think, originally, it was that a non-backward-compatible package had
to use a different name (say, package `foo` must then be released as
under the package name `foo2`). I don't know whether that's the current
policy.
(I'm not picking on this interesting-sounding calendar library. Just
wondering about the general question, since I haven't decided how to
version my own packages in the new package system.)
Neil V.
--
You received this message because you are subscribed to the Google Groups "Racket
Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/racket-dev/55E46464.3070603%40neilvandyke.org.
For more options, visit https://groups.google.com/d/optout.
