docs: add RELEASING.md #146
Conversation
Signed-off-by: Niels Pardon <par@zurich.ibm.com>
benbellick
left a comment
benbellick
left a comment
There was a problem hiding this comment.
LGTM. I haven't actually done the release here, so might make sense to leave it to @tokoko to actually confirm this if you aren't confident.
In the future, will it be possible to automate this process even more? It would be great if the versions could get bumped automatically based off of if there are breaking changes or not. I think some of the other repos do this.
I did the release this way this morning so I know this is how it works currently. @tokoko only very recently became committer and I don't see him having performed a release of this repo. I had asked @mbrobbel on Slack who has done recent releases of this repo for a documentation of the release process but haven't gotten any response.
I guess so. I'm just trying to document the existing release process given that there is currently no documentation at all. |
Co-authored-by: Ben Bellick <36523439+benbellick@users.noreply.github.com>
Signed-off-by: Niels Pardon <par@zurich.ibm.com>
tokoko
left a comment
tokoko
left a comment
There was a problem hiding this comment.
Haven't done a release before either, but if it worked on the latest one, it's probably correct :)
|
@nielspardon Ah yes fair enough! Looks good then :) |
|
Created #147 as work for later to figure out automatic version bumping. |
3 participants
No description provided.