On Mon, Aug 31, 2015 at 10:27 AM, Neil Van Dyke <[email protected]> wrote: > What's the current new package system policy on non-backward-compatible > changes in a package version?
Good question. > > 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. That was my understanding, too, though, as you can see, I didn't do that. My reasoning went like this: - As far as I know, no one is using this library. (But, if anyone is, please let me know.) - It's actually extremely unlikely that the changes would break any existing code, even if the library were being used. (But, if I have broken your code, again, please let me know.) -Jon -- 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/CAKfDxxxamkGxZ9PsJtQxQMDzcpurJSEjge6-D7QhnrvpryT39A%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
