Release Process Updates (#468)

Co-authored-by: Ray Douglass <3107146+raydouglass@users.noreply.github.com>
Co-authored-by: aravenel <ravenel@gmail.com>
Co-authored-by: Bradley Dice <bdice@bradleydice.com>

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}