You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: release-team/role-handbooks/release-team-lead/README.md
+4-1Lines changed: 4 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -168,7 +168,10 @@ cc @release-team-leads
168
168
## Working with the Release Team Calendar
169
169
170
170
To get access to the [release team calendar](https://calendar.google.com/calendar/embed?src=kipmnllvl17vl9m98jen6ujcrs%40group.calendar.google.com) reach out to a SIG Release tech lead or chair.
171
-
Its useful to add major events of the release cycle to the calendar e.g. Enhancements Freeze, Code Freeze and Test Freeze.
171
+
It's useful to add major events of the release cycle to the calendar e.g. Enhancements Freeze, Code Freeze and Test Freeze.
172
+
173
+
It is also useful to add estimated release cut dates to the calendar e.g. 1.XX.0-alpha.1. Cuts are typically scheduled for
174
+
Wednesdays, but can be moved to a different day if needed or based on the Branch Manager's availability.
172
175
173
176
**Additional tips:**
174
177
- Add a calendar entry for the time period before Enhancements Freeze with the title [1.xx] Enhancements Freeze coming on HH:mm PDT Month Day, Year
0 commit comments