Skip to content
代码片段 群组 项目
未验证 提交 f87e14fd 编辑于 作者: Evan Read's avatar Evan Read 提交者: GitLab
浏览文件

Merge branch 'docs-patch-release-twice-monthly' into 'master'

Clarify ambiguous term regarding patch release schedule

See merge request https://gitlab.com/gitlab-org/gitlab/-/merge_requests/173503



Merged-by: default avatarEvan Read <eread@gitlab.com>
Co-authored-by: default avatarMatthew Badeau <mbadeau@gitlab.com>
No related branches found
No related tags found
无相关合并请求
......@@ -39,7 +39,7 @@ The following table describes the version types and their release cadence:
|:-------------|:------------|:--------|
| Major | For significant changes, or when any backward-incompatible changes are introduced to the public API. | Yearly. The next major release is GitLab 18.0, scheduled for May 15th, 2025. GitLab [schedules major releases](https://about.gitlab.com/releases/) for May each year, by default. |
| Minor | For when new backward-compatible functionality is introduced to the public API, a minor feature is introduced, or when a set of smaller features is rolled out. | Monthly, scheduled for the third Thursday of each month. |
| Patch | For backward-compatible bug fixes that fix incorrect behavior. See [Patch releases](#patch-releases). | Bi-monthly, scheduled for the Wednesday the week before and the Wednesday the week after the monthly minor release. |
| Patch | For backward-compatible bug fixes that fix incorrect behavior. See [Patch releases](#patch-releases). | Twice monthly, scheduled for the Wednesday the week before and the Wednesday the week after the monthly minor release. |
## Upgrade recommendations
......
0% 加载中 .
You are about to add 0 people to the discussion. Proceed with caution.
先完成此消息的编辑!
想要评论请 注册