tree bb62bb8eb587d20d2426a8eaf9f7edd2dfc45f40
parent 1cecfeb6894c2cbcf619a03313fdf731306caee5
author Dmitri Shuralyov <dmitshur@golang.org> 1541188056 -0400
committer Dmitri Shuralyov <dmitshur@golang.org> 1541191356 +0000

maintner/maintnerd: change definition of Go release to require release branch

Previously, the list-Go-releases RPC endpoint was more flexible and
considered a Go release to exist as long as there's a git tag for it,
regardless of whether a corresponding release branch existed.

Such a situation is very unlikely to come up, and we don't want to cause
all users of this API to filter out releases without a release branch.
So just re-define a Go release to require a release branch, and
make that the API promise.

In practice, this should not have any effect because all go tags
have corresponding release branches.

Updates golang/go#17626

Change-Id: Ia7a8354000483c969e123f0f3605fd360846c40b
Reviewed-on: https://go-review.googlesource.com/c/147200
Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>