Delivery::Deployments FY25 Q1 OKRs ideas and discussion
Context
We are few weeks away from FY25 Q1 and it is time to start planning for OKRs. Let's use this issue to suggest possible ideas and discuss the best combination of ideas and scope to set us up for Q1.
FY24 Q4 State
As Delivery::Orchestration great progress has been made on the Security Release process and automation domain in the last quarters through:
- Automating and combining bug fixes and security fixes into patch releases
- Reduce Security release preparation to less than 24hrs
- The work on Creating Release Environments, for testing new releases in the supported maintenance policy restarted, and it has made significant progress.
- We are currently in the final weeks of the Pilot of two scheduled security releases per month in preparation for planned releases
The Delivery::System team made significant progress in bringing the Dedicated Tenant Upgrades to Zero Downtime.
FY25 Q1 - What's next?
We have plenty of work to iterate further on the FY24 Q4 projects.
- Should we look at changes to our deployment pipelines to split out by environment(s)?
- Related to splitting out deployments by environments, what about by service/type of deployment?
- What further improvements do we need to do for deployments to dedicated?
- What wrap up for Release Environments do we need to do?
- What tech debt do we have that needs to be taken care of?
What about Cells?
With Cells moving to an earlier timeline with a different initial design it is time to start thinking about an Objective that could bring us a step closer to the solution. Considering that the first iteration of Cells will be fully based on Dedicated and we are gaining expertise in how to Release to Dedicated, are there opportunities for the Delivery::Release team in that direction?
Please let's share our OKR ideas for Q1.
cc @rpereira2, @ggillies, @vglafirov, @anganga, @nolith, @skarbek