Blog post: http://blog.racket-lang.org/2015/10/retiring-unstable.html
Announcement item: * The `unstable-*` packages are out of the main distribution. Most of their contents have been either merged with established Racket libraries or spun off as their own packages. This change is backwards compatible for packages that properly list their dependencies. Full details: http://blog.racket-lang.org/2015/10/retiring-unstable.html Vincent On Fri, 30 Oct 2015 14:09:15 -0500, Vincent St-Amour wrote: > > That sounds like a good plan. > > Individual additions are already documented with history annotations in > the docs (and most are too small to be included in the release notes of > their respective libraries), but a discussion of the overall changes, > with full detail, would be nice to have. I'll write that. > > For now, I'm thinking of putting that on the blog, and in the `unstable` > release notes. I'm less sure about the latter, though, since `unstable` > is not actually part of the release anymore, but that's the one central > location where that info would make sense. > > Vincent > > > > > On Fri, 30 Oct 2015 13:59:57 -0500, > Neil Van Dyke wrote: > > > > Asumu Takikawa wrote on 10/30/2015 02:44 PM: > > > On 2015-10-30 13:39:48 -0500, Vincent St-Amour wrote: > > >> For the unstable changes, how much detail do we want? Listing the fate > > >> of each of the 40+ unstable subcollects is probably too much, but just > > >> saying "unstable is out of the distribution, some of its goodies have > > >> been merged" is probably too little. Any thoughts? > > > How about blogging in detail about the changes and then just linking to > > > the > > > blog entry? (in addition to that short blurb) > > > > What Asumu said, except that one time-honored engineering convention > > would be for the detail to go into the release notes (in whatever form > > that the release notes are currently kept). > > > > If you wanted to, you could *also* put the detail into a blog entry, in > > addition to in the release notes, but the release notes would be the > > normative reference, and the blog entry would link to the release notes. > > > > 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/5633BE2D.10208%40neilvandyke.org. > > For more options, visit https://groups.google.com/d/optout. -- 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/m2pozwc9zx.wl-stamourv%40eecs.northwestern.edu. For more options, visit https://groups.google.com/d/optout.
