From 3642edd254c04103eb8bd93aca4ba21a4d7e1d76 Mon Sep 17 00:00:00 2001 From: caryr35 Date: Tue, 27 Feb 2024 11:36:36 -0500 Subject: [PATCH] Release Process Updates (#468) Co-authored-by: Ray Douglass <3107146+raydouglass@users.noreply.github.com> Co-authored-by: aravenel Co-authored-by: Bradley Dice --- releases/process.md | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/releases/process.md b/releases/process.md index 8aae3e04028..fce259009f2 100644 --- a/releases/process.md +++ b/releases/process.md @@ -105,10 +105,11 @@ Generally the process for Code Freeze occurs around 10:00AM PT on the first day Project Leads {: .label .label-blue} -1. Move any open pull requests targeting `branch-M.B` to target `branch-M.C` instead -2. Wait for confirmation from operations on the branch switch -3. Continue `M.C` development -4. Respond promptly to operations if any issues are found with the `M.B` release +1. Inform operations team of any new release artifacts (packages, wheels, containers) no later than 2 weeks prior to cuDF burndown +2. Move any open pull requests targeting `branch-M.B` to target `branch-M.C` instead +3. Wait for confirmation from operations on the branch switch +4. Continue `M.C` development +5. Respond promptly to operations if any issues are found with the `M.B` release Operations {: .label .label-purple}