Release policies #478
joeblubaugh
started this conversation in
General
Replies: 1 comment 1 reply
|
That's a good question. So far I've created releases every now and then when it seemed to make sense given the changes since the last one. But this has to become a bit more automated. As a first step, I've created automated nightly releases. Also just published v1.4.2 |
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Should users request a new tagged release if they want to use certain features? This improves compatibility with
go get.Should there be a regular release cadence, or a policy on when enough changes have accumulated to justify a new release?
All reactions