aaaaaa cutting an open source release if hard how do you decide when something is enough changes for a release when more just keep coming in
i've solved the problem I'm just gonna do 0.2.0-snapshot.N until we come up with something better
un mir zaynen ale shvester
- they/she
- github.com/coolreader18
known compiler nerd. jewish, ws71. i'm a maintainer of RustPython (bit less active though cause of ✨burnout✨) and i like open source and rust in general
You must log in to comment.
in reply to @coolreader18's post:
For non-breaking changes my philosophy is to release pretty much whenever I have the time; I still don’t have the knack of breaking ones (though doing things like release candidates or alpha releases can help)