@samth, @mflatt, or any other core racket devs: what’s the versioning policy for the base package? when do I bump it and which part should I bump?
@mflatt has joined the channel
@notjack set the channel topic: This channel is for discussion about developing the Racket language and standard distribution. See also the racket-dev mailing list.
@notjack set the channel topic: Discussion about developing the Racket language and standard distribution. See also the racket-dev mailing list.
@notjack set the channel topic: Discussion about developing the Racket language and standard distribution.
@notjack set the channel purpose: Discussion about developing the Racket language and standard distribution. See also the racket-dev mailing list.
The base version needs to stay in sync with the Racket version. So, it mostly gets bumped when there’s a “.zo” compatibility issue, but it could also get bumped for significant new functionality in the core racket collection.
So if I added a sequence->vector function to racket/vector, would that be significant enough to warrant bumping it at all?
It would be fine to increase the version in that case. I wouldn’t bother myself, though, unless I needed to declare a dependency somewhere.