Release Management scheduling issue - FY24 Q1 & Q2
Previously @amyphillips and @mbursi have created a release management schedule by talking to you each individually to check availability. This is difficult to scale, so we'll try a signup issue for the next few milestones.
Please put your name down for the milestones you would be available to cover. This means that writing your name down for three milestones will not result in you being assigned all three or having to cover more milestones in a row. The name is only representing availability for that particular milestone.
On the due date, @amyphillips and @mbursi will work through all the options and create an MR with a resulting sustainable schedule for you all to approve. We will try to avoid having RM rotations with all the team members belonging to the same team to give each team enough time to carry on project work.
If you're not yet trained in release management, please sign up anyway. We'll arrange training around your first shift.
Milestone | Dates | EMEA | AMER |
---|---|---|---|
15.11 | 23rd March - 22nd April | @vglafirov, @ahyield | @mayra-cabrera, @sabrams, @jennykim-gitlab |
16.0 | 23rd April - 22nd May | @rpereira2, @ahyield | @jennykim-gitlab, @mayra-cabrera, @sabrams |
16.1 | 23rd May - 22nd June | @ahyield, @nolith, @rpereira2 | @skarbek, @jennykim-gitlab, @mayra-cabrera |
16.2 | 23rd June - 22nd July | @ahyield, @nolith, @rpereira2 | @jennykim-gitlab, @mayra-cabrera |