Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Kuadrant Release Process #46

Merged
merged 17 commits into from
Feb 21, 2024
Merged

Kuadrant Release Process #46

merged 17 commits into from
Feb 21, 2024

Conversation

didierofrivia
Copy link
Member

@didierofrivia didierofrivia commented Jan 11, 2024

Partially closes #59

Technical aspects of the process: #41

@didierofrivia didierofrivia added the RFC Request For Comments label Jan 11, 2024
@didierofrivia didierofrivia self-assigned this Jan 11, 2024
rfcs/0000-kuadrant-release-process.md Outdated Show resolved Hide resolved
rfcs/0000-kuadrant-release-process.md Outdated Show resolved Hide resolved
rfcs/0000-kuadrant-release-process.md Outdated Show resolved Hide resolved
rfcs/0000-kuadrant-release-process.md Outdated Show resolved Hide resolved
rfcs/0000-kuadrant-release-process.md Outdated Show resolved Hide resolved
rfcs/0000-kuadrant-release-process.md Outdated Show resolved Hide resolved
rfcs/0000-kuadrant-release-process.md Outdated Show resolved Hide resolved
rfcs/0000-kuadrant-release-process.md Outdated Show resolved Hide resolved
rfcs/0000-kuadrant-release-process.md Outdated Show resolved Hide resolved
rfcs/0000-kuadrant-release-process.md Outdated Show resolved Hide resolved
@didierofrivia didierofrivia marked this pull request as ready for review January 17, 2024 13:55
@alexsnaps alexsnaps added the status/FCP Final Comment Period label Feb 13, 2024
@alexsnaps
Copy link
Member

Added the "Final Comment Period" to this RFC, so please try to consolidate responses within the coming week...
Other than major disagreement, we shall merge this after this period.

Copy link
Contributor

@eguzki eguzki left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

left some comments

rfcs/0000-kuadrant-release-process.md Outdated Show resolved Hide resolved
other teams within the organization. A few examples of the communication channels that need to be updated are:

- Changelog generation
- Release notes
Copy link
Contributor

@eguzki eguzki Feb 16, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I like how Istio is doing this. Simple and clear.

Release announcements

Screenshot 2024-02-16 at 14-59-30 Release Announcements

X.Y.x patch releases

Screenshot 2024-02-16 at 15-00-23 1 20 x Releases

New release notes

Screenshot 2024-02-16 at 15-00-52 Announcing Istio 1 20 3

rfcs/0000-kuadrant-release-process.md Outdated Show resolved Hide resolved
* A brief process from QA to asserting a release candidate
* TLS and DNS policies are managed by the Kuadrant Operator
Copy link
Contributor

@guicassolato guicassolato left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice job, @didierofrivia!

* Kuadrant Suite version will have the Kuadrant Operator version
* The rest of the dependencies are versioned independently
@didierofrivia didierofrivia merged commit fa64f6c into main Feb 21, 2024
1 check passed
@didierofrivia didierofrivia deleted the kuadrant-release-process branch February 21, 2024 11:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
RFC Request For Comments status/FCP Final Comment Period
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

Kuadrant Release Process
7 participants