April 9th in the #general Slack channel taught me that there was no clean way to release a breaking change in a package. I'm open to working on version pinning support in raco pkg provided that a maintainer can walk me through some code.
In the meantime, as much as I appreciate the efforts made in the current system, I'm considering stopping my contributions to the package catalog until further notice. I'm open to submitting packages if I am confident in their longevity, but I don't want to end up in the position I've been in for the last few weeks when planning a release. That position being an inability to release an edition that is not in some way "aware" of a prior edition. In my view, changing the package/collection name is an example of that problem, not a solution to it. I'm considering asking my users to specify different package sources in their info.rkt files when dealing with my work. Before I commit to that decision, I wanted to tap into those of you who have already been here. How have you handled breaking changes for your projects? How have you communicated with your users to make sure they were adequately prepared? Am I being too black-and-white about this? ~slg -- You received this message because you are subscribed to the Google Groups "Racket Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to racket-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/racket-users/3tKIr3GrU9Jnl7V-5yzb52OL3mjt8XNe9F_Qv9HDKwy8xC4j9lQo2e5eGSle4ZFHAee_FiGVhr15lXoovUE6yqoARP-ZNi3kXXz8ETXdufg%3D%40sagegerard.com.
