imjoey commented on a change in pull request #143: URL: https://github.com/apache/apisix-website/pull/143#discussion_r558895150
########## File path: docs/release-guide.md ########## @@ -3,6 +3,43 @@ id: release-guide title: Release Guide --- +## Release Flow + +The release flow of Apache APISIX follows [GitLab flow](https://docs.gitlab.com/ee/topics/gitlab_flow.html), instead of Git flow or Github flow. Furthermore, [Release branches with GitLab flow](https://docs.gitlab.com/ee/topics/gitlab_flow.html#release-branches-with-gitlab-flow) is the preferred way. The chart below will take the release `v2.3` of [apache/apisix-dashboard](https://github.com/apache/apisix-dashboard) as an example to illustrate the details. + + + +The entire flow is comprised of the following four phases. + +### Planning Phase + +This phase will decide if a feature is ready to be released as well as the release time. + +- A new target milestone will be created in Github. (e.g. [`2.3`](https://github.com/apache/apisix-dashboard/milestone/6)) +- A discussion will be started on devel mailing list [[email protected]]([email protected]) for gathering ideas for the next release +- Maintainer team will then mark the issues and pull requests with the target milestone + +### Development Phase + +This phase is for deveoping new features and fix bugs. + +- Maintainer team and contributors will work for the issues targeted to release milestone +- Every single new issue is required to be recognized if should be included in the next release. If yes, the milestone needs to be set for the issue Review comment: @juzhiyuan `if` means `whether`, `it` may not be proper here. ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
