Automated Releases

[shaneutt]

What would you like to be added:

Automated release creation.

Why this is needed:

It's nice to have and it might encourage us to release more often.

Details:

Ideally we would create a (github?) workflow which automates creating a Github release for us with the following criteria:

1. if using Github actions, has workflow_dispatch: property to allow manual triggering with parameters
2. runs any tests needed for the release
3. automatically fills in the CHANGELOG for the release
4. automatically builds and uploads all release artifacts (the release yaml namely)
5. automatically takes SHA256SUM checks of all release artifacts and uploads them to the release
6. automatically creates a github discussion announcing the release
7. saves the release as draft so that a human can review and publish

TODO:

• Before resolving this issue we should make sure to record whatever changes were made as updates to RELEASE.md.

[youngnick]

One thousand percent agreed, the more we can head towards this goal, the better.

[akankshakumari393]

Hey @youngnick @shaneutt. Is this issue still valid. I would like to contribute to it. Also I would need some technical guidance on it.

[shaneutt]

Still valid, feel free to ask in this issue if you need help or run into any specific problems.

[akankshakumari393]

/assign

[akankshakumari393]

feel free to ask in this issue if you need help or run into any specific problems.
Sure thanks @shaneutt 👍🏻

[akankshakumari393]

I would like to understand how were we releasing up until now. Was it a manual process?

[shaneutt]

It's been this so far: https://github.com/kubernetes-sigs/gateway-api/blob/main/RELEASE.md#release-steps

[youngnick]

Hi @akankshakumari393, before we go too far down the automation route, we have #916 and #627 that are both v0.6.0 release blockers that we could really use help on.

[akankshakumari393]

yeah Sure that, I would be happy to help.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all PRs.

This bot triages PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

• Mark this PR as fresh with /remove-lifecycle stale
• Close this PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[shaneutt]

We want this feature, but we consider it low priority until v1.0.0/GA is complete and don't believe we will have bandwidth for it until then.

[shaneutt]

There haven't been enough pain points to push this forward, so we're going to close it for now. It is always available to re-open if things change.