Release process #5947
redscholar
started this conversation in
General
Release process
#5947
Replies: 2 comments
-
The release cycle is typically 2 weeks, with 1 week for development and 1 week for testing. issue range should align with the version cycle. |
Beta Was this translation helpful? Give feedback.
0 replies
-
About release noteWe will generate a changelog based on the release notes in the PRs. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Confirm release range
In the community meeting, determine which issues and PRs should be included in this release and set deadlines for each phase.
Fixed and closed issues
Developers work on resolving their respective issues, write unit tests, and perform self-testing. After passing the tests, they submit their code.
Merge code to release branch
Merge the submitted code and synchronize it with the branch that needs to be released (e.g., release-x).
The repositories involved include: kubesphere,console,ks-installer
Daily build
Every day, test versions (xxx-alpha or xxx-rc) are generated for merged code. These test versions require functional testing and end-to-end testing.
Test Phase
If there are too many issues, testing intervention is needed.
Trigger release process
Using
/release xxx
to trigger the release process (currently not supported).Beta Was this translation helpful? Give feedback.
All reactions