Remove Feature Freeze from Chromium release docs
Chromium Browser no longer relies on Feature Freeze Bug: 377928604 Change-Id: Ie6e951c9353d5e0ee435f7a9fe6035bbf78b67f1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6192283 Reviewed-by: Erhu Akpobaro <eakpobaro@google.com> Commit-Queue: Harry Souders <harrysouders@google.com> Cr-Commit-Position: refs/heads/main@{#1410433}
This commit is contained in:

committed by
Chromium LUCI CQ

parent
edda3d6a40
commit
b3126718e4
docs
@ -48,26 +48,25 @@ milestone proceeds through our release cycle:
|
||||
our [release calendar](https://chromiumdash.appspot.com/schedule).
|
||||
* Some dates will vary between different platforms; see the release calendar
|
||||
for specifics dates for each platform.
|
||||
* Feature freeze and branch point dates are fixed, but release dates are
|
||||
* Branch point dates are fixed, but release dates are
|
||||
subject to change based on a variety of factors (e.g. late-breaking
|
||||
regressions).
|
||||
* Release dates are adjusted to avoid shipping new milestones to stable around
|
||||
major holidays to ensure proper coverage if issues arise. These adjustments
|
||||
are already depicted in our release schedule.
|
||||
|
||||
### Feature Freeze
|
||||
|
||||
All new features planned to launch in this milestone should be code complete
|
||||
(all primary functionality implemented) by feature freeze. Features which are
|
||||
not code complete by feature freeze should be punted to the following
|
||||
milestone.
|
||||
|
||||
### Branch Point
|
||||
|
||||
The branch generated by the daily canary created at branch point is
|
||||
designated as the milestone branch, which is then stabilized over the following
|
||||
four weeks. All strings should be landed by branch point, and all beta blocking
|
||||
bugs should be addressed as well.
|
||||
The branch generated by the daily canary created at branch point is designated
|
||||
as the milestone branch, which is then stabilized over the following four weeks.
|
||||
|
||||
Before Branch Point:
|
||||
|
||||
1. All new features planned to launch in this milestone should be code complete
|
||||
(all primary functionality implemented). Features which are not code
|
||||
complete by branch point should be punted to the following milestone.
|
||||
2. All strings should be landed.
|
||||
3. All beta blocking bugs should be addressed.
|
||||
|
||||
Please consider [these guidelines](../release_branch_guidance.md) when landing
|
||||
code around branch point.
|
||||
|
@ -17,6 +17,5 @@
|
||||
* Prioritize stability and "bake time", as well as other ways to reduce the
|
||||
release risk in your timeline discussions.
|
||||
* Consider API adoption timelines: code may not be exercised until developers
|
||||
adopt API, so feature freeze and branch could have minimal impact on
|
||||
stability.
|
||||
adopt API, so branch could have minimal impact on stability.
|
||||
|
||||
|
Reference in New Issue
Block a user