Skip to content

cmd/go: build tags for beta and RC builds clarification #26458

@dlsniper

Description

@dlsniper

Hi,

I would like to get some clarification about how the build tags for Go versions work.

For example, we have now Go 1.11 Beta 1, which I would expect to use the go1.11beta1 build tag and, when Go 1.11 RC 1 is released, I would expect to have go1.11rc1 used. When Go 1.11 is released, I would expect to see go1.11 flag working.

However, currently Go 1.11 Beta 1 seems to use go1.11 as build tag. Normally, I would expect this to be a bug, since go1.11 > go1.11beta1 regarding release versions.

Have I missed something from the way build tags should work? Or if this is undocumented/unwritten can we please get some more official information on it?

Thank you.

Metadata

Metadata

Assignees

No one assigned

    Labels

    DocumentationIssues describing a change to documentation.FrozenDueToAgeNeedsFixThe path to resolution is known, but the work has not been done.

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions