remote-apis
remote-apis copied to clipboard
Please tag REv2 2.1.0 2.2.0 [...]
The latest version of REv2 that has been tagged is 2.0.0. Let's add tags for some of the historical releases we did, so that it's clear to implementors what versions they should be announcing. This is especially important, now that Bazel is going to conditionally set output_paths
based on the version announced by the server.
This commit seems to be the first mention of 2.1: https://github.com/bazelbuild/remote-apis/commit/b5123b1bb2853393c7b9aa43236db924d7e32d61
2.2: https://github.com/bazelbuild/remote-apis/commit/ddca4b2c4487853f88c0e8f99bd4a0f485aeaf42
2.3: https://github.com/bazelbuild/remote-apis/commit/e1fe21be4c9ae76269a5a63215bb3c72ed9ab3f0
2.3 should also include commit e95641649b5b4d3c582c89daabfaabeb8189dd77.
Considering that both https://github.com/bazelbuild/remote-apis/commit/e1fe21be4c9ae76269a5a63215bb3c72ed9ab3f0 and https://github.com/bazelbuild/remote-apis/commit/e95641649b5b4d3c582c89daabfaabeb8189dd77 were more than a year ago, I'm assuming that v2.3.0 should also be released then. Let me patch up Buildbarn to properly announce itself as v2.3.0.
In our last meeting, I think somebody asked for a git tag creation instruction?
> git clone https://github.com/bazelbuild/remote-apis.git
> cd remote-apis
> git tag v2.2.0 ddca4b2
> git tag v2.1.0 b5123b1
...
> git push --tags origin
Then you should be able to use the UI in https://github.com/bazelbuild/remote-apis/releases to create a release for each tag.
I have tagged v2.1.0-rc1, v2.2.0-rc1, and v2.3.0-rc1. Assuming those releases look good, I will promote them soon.
Given that we fell off the bandwagon on creating proper releases for a bit, my inclination is to tag head as v2.4.0, then try to be better about releases in the future. That's likely somewhat wrong, though, because I suspect there's more than one change that would require a version rev between 2.3.0 and head--I just don't know how much value trying to create a trail of proper releases really adds. Will discuss at the RE API sync.
I have published the official release of v2.1.0 and v2.2.0. I have also published v2.3.0-rc2, which includes https://github.com/bazelbuild/remote-apis/commit/e95641649b5b4d3c582c89daabfaabeb8189dd77.
I have not yet gone through the remaining commits to decide if a v2.4.0 (or other versions) is warranted.