From 89f3ae5ae65de412bdde50e6e01ca666a1b7c2bb Mon Sep 17 00:00:00 2001 From: Mike Frysinger Date: Wed, 8 Jul 2020 15:02:39 -0400 Subject: [PATCH] release-process: document schedule (including freezes) publicly Change-Id: Ic037b54630017740d7859292b32b8c57f4af7854 Reviewed-on: https://gerrit-review.googlesource.com/c/git-repo/+/274772 Tested-by: Mike Frysinger Reviewed-by: Jonathan Nieder --- docs/release-process.md | 32 ++++++++++++++++++++++++++++++++ release/sign-tag.py | 6 +----- 2 files changed, 33 insertions(+), 5 deletions(-) diff --git a/docs/release-process.md b/docs/release-process.md index 93a0f3e0..0df590ac 100644 --- a/docs/release-process.md +++ b/docs/release-process.md @@ -5,6 +5,37 @@ related topics and flows. [TOC] +## Schedule + +There is no specific schedule for when releases are made. +Usually it's more along the lines of "enough minor changes have been merged", +or "there's a known issue the maintainers know should get fixed". +If you find a fix has been merged for an issue important to you, but hasn't been +released after a week or so, feel free to [contact] us to request a new release. + +### Release Freezes {#freeze} + +We try to observe a regular schedule for when **not** to release. +If something goes wrong, staff need to be active in order to respond quickly & +effectively. +We also don't want to disrupt non-Google organizations if possible. + +We generally follow the rules: + +* Release during Mon - Thu, 9:00 - 14:00 [US PT] +* Avoid holidays + * All regular [US holidays] + * Large international ones if possible + * All the various [New Years] + * Jan 1 in Gregorian calendar is the most obvious + * Check for large Lunar New Years too +* Follow the normal [Google production freeze schedule] + +[US holidays]: https://en.wikipedia.org/wiki/Federal_holidays_in_the_United_States +[US PT]: https://en.wikipedia.org/wiki/Pacific_Time_Zone +[New Years]: https://en.wikipedia.org/wiki/New_Year +[Google production freeze schedule]: http://goto.google.com/prod-freeze + ## Launcher script The main repo script serves as a standalone program and is often referred to as @@ -242,6 +273,7 @@ Things in italics are things we used to care about but probably don't anymore. | Apr 2020 | **Apr 2030** | | | **20.04 Focal** | 2.25.0 | 2.7.17 3.7.5 | +[contact]: ../README.md#contact [rel-d]: https://en.wikipedia.org/wiki/Debian_version_history [rel-g]: https://en.wikipedia.org/wiki/Git#Releases [rel-p]: https://en.wikipedia.org/wiki/History_of_Python#Table_of_versions diff --git a/release/sign-tag.py b/release/sign-tag.py index 09f89187..605437c9 100755 --- a/release/sign-tag.py +++ b/release/sign-tag.py @@ -18,11 +18,7 @@ This is intended to be run only by the official Repo release managers, but it could be run by people maintaining their own fork of the project. -NB: Avoid new releases on off-hours. If something goes wrong, staff/oncall need -to be active in order to respond quickly & effectively. Recommend sticking to: -* Mon - Thu, 9:00 - 14:00 PT (i.e. MTV time) -* Avoid US holidays (and large international ones if possible) -* Follow the normal Google production freeze schedule +NB: Check docs/release-process.md for production freeze information. """ import argparse