Plans for tags/releases for the project?

[vishaltak]

Hello Team 👋🏼

Since the project has moved from Pagure to this repository, no tags/releases have been created in this repository. We plan to use this repository to build s FIPS-enabled-Go for our environment. Currently, we are building from the relevant branches. However, it is generally recommended to use tags/releases instead of branches.

Questions

• Does the team have plans to sync the tags/releases from Pagure to this repository?
• If not, does the team plan to create tags/releases going forward?

Thanks 🙇🏼

[derekparker]

Thanks for opening this issue! We will be syncing tags over to this repo, it just hasn't happened yet. I'll make sure to sync them soon!

[stanhu]

@derekparker Thanks for pushing the Go 1.17.10 tag. Would you be able to push tags for the earlier versions?

[bosdhill]

As an aside, I've noticed that the go version in the VERSIONS file didn't get updated in the 1.18.2 release https://github.com/golang-fips/go/blob/go1.18.2-1-openssl-fips/VERSION

[derekparker]

As an aside, I've noticed that the go version in the VERSIONS didn't get updated in the 1.18.2 release https://github.com/golang-fips/go/blob/go1.18.2-1-openssl-fips/VERSION

Great catch, we'll make sure to get that updated in the next rebase (or possibly before).

[twk3]

@derekparker with the 1.17.13 change merged, can we get a tagged release for that version?

[derekparker]

@twk3 I've tagged 1.17.13 and 1.18.5. I will tag 1.18.6 when it's merged.

[twk3]

@derekparker many thanks! Sorry I had been looking at the releases page, and didn't notice you had tagged.