juzhiyuan commented on a change in pull request #143:
URL: https://github.com/apache/apisix-website/pull/143#discussion_r558893937



##########
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.
+
+![Release Flow](/img/release_flow.png)

Review comment:
       🤔 Links start with `static.apiseven.com` are from blogs.
   
   fine, I know what happened, once we merged and deployed, it will show 
correctly。

##########
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.
+
+![Release Flow](/img/release_flow.png)

Review comment:
       🤔 Links start with `static.apiseven.com` are from blogs.
   
   fine, I know what happened, once we merged and deployed, it will show 
correctly.




----------------------------------------------------------------
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]


Reply via email to