You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There's currently two Git tags defined in bazelbuild/remote-apis:
Tag v2.0.0 is commit e77c4eb and is (hopefully) what implementations mean by SemVer { major: 2 }.
Tag 4ac0011 is commit 4ac0011 and is of unknown meaning.
The comments in remote_execution.proto refer to changes in minor versions v2.1, v2.2, and v2.3 which are not tagged. This makes it difficult to determine which behavior a conforming implementation should have at each version.
Given that there's now multiple APIs specified, and multiple versions of the Remote Execution API, would it be possible to add additional tags? For example:
execution/v2.0, execution/v2.1, execution/v2.2, and execution/v2.3 that can be used as stable references for a given version of remote_execution.proto
asset/v1.0 and logstream/v1.0 for similar purposes in the remote_asset.proto and remote_logstream.proto files.
The text was updated successfully, but these errors were encountered:
There's currently two Git tags defined in bazelbuild/remote-apis:
v2.0.0
is commit e77c4eb and is (hopefully) what implementations mean bySemVer { major: 2 }
.4ac0011
is commit 4ac0011 and is of unknown meaning.The comments in
remote_execution.proto
refer to changes in minor versions v2.1, v2.2, and v2.3 which are not tagged. This makes it difficult to determine which behavior a conforming implementation should have at each version.Given that there's now multiple APIs specified, and multiple versions of the Remote Execution API, would it be possible to add additional tags? For example:
execution/v2.0
,execution/v2.1
,execution/v2.2
, andexecution/v2.3
that can be used as stable references for a given version ofremote_execution.proto
asset/v1.0
andlogstream/v1.0
for similar purposes in theremote_asset.proto
andremote_logstream.proto
files.The text was updated successfully, but these errors were encountered: