The following table shows the preliminary dates for the v1.8 release cycle.
| What | Who | When | Week |
|---|---|---|---|
| Start of Release Cycle | Release Lead | Monday 22nd April 2024 | week 1 |
| v1.7.x released [1] | Release Lead | Tuesday 23rd April 2024 | week 1 |
| Schedule finalized | Release Lead | Friday 26th April 2024 | week 1 |
| Team finalized | Release Lead | Friday 26th April 2024 | week 1 |
| v1.6.x & v1.7.x released | Release Lead | Tuesday 14th May 2024 | week 4 |
| v1.6.x & v1.7.x released | Release Lead | Tuesday 11th June 2024 | week 8 |
| v1.6.x & v1.7.x released | Release Lead | Tuesday 9th July 2024 | week 12 |
| v1.8.0-beta.0 released | Release Lead | Tuesday 16th July 2024 | week 13 |
| Communicate beta to providers | Release Lead | Tuesday 16th July 2024 | week 13 |
| v1.8.0-beta.x released | Release Lead | Tuesday 23rd July 2024 | week 14 |
| release-1.8 branch created (Begin [Code Freeze]) | Release Lead | Tuesday 30th July 2024 | week 15 |
| v1.8.0-rc.0 released | Release Lead | Tuesday 30th July 2024 | week 15 |
| release-1.8 jobs created | Release Lead | Tuesday 30th July 2024 | week 15 |
| v1.8.0-rc.x released | Release Lead | Tuesday 6th August 2024 | week 16 |
| v1.8.0 released | Release Lead | Monday 12th August 2024 | week 17 |
| v1.6.x & v1.7.x released | Release Lead | Monday 12th August 2024 | week 17 |
| v1.8.1 released (tentative) | Release Lead | Thursday 15th August 2024 | week 17 |
| Organize release retrospective | Release Lead | TBC | week 17 |
After the .0 the .1 release will be created to ensure faster Kubernetes support after K8s 1.31.0 will be available.
After the .1 we expect to release monthly patch release (more details will be provided in the 1.9 release schedule).
Note: This release cycle there are some additional constraints for the .1 release due to planned test infra activities; as a consequence .1 timeline has been compressed (from 1 week / 10 days delay of the last release cycle down to 2/3 days) and maintainers might change plans also last second to adapt to latest info about infrastructure availability.
| Role | Lead (GitHub / Slack ID) | Team member(s) (GitHub / Slack ID) |
|---|---|---|
| Release Lead | Muhammad Adil Ghaffar (@adilGhaffarDev / @adil) |
Dan Buch (@meatballhat / @meatballhat) Nivedita Prasad (@Nivedita-coder / @Nivedita Prasad) Chirayu Kapoor (@chiukapoor / @Chirayu Kapoor) David Hwang (@dhij / @David Hwang) |
| Communications/Docs/Release Notes Manager | Chandan Kumar (@chandankumar4 / @Chandan Kumar) |
Vishal Anarase (@vishalanarase / @Vishal Anarase) Shipra Jain (@shipra101 / @Shipra Jain)Rajan Kumar Jha (@rajankumary2k / @Rajan Jha)Kunju Perath (@kperath / @Kunju Perath) |
| CI Signal/Bug Triage/Automation Manager | Sunnat Samadov (@Sunnatillo / @Sunnat) |
Willie Yao (@willie-yao / @willie) Troy Connor (@troy0820 / @troy0820) Jayesh Srivastava (@jayesh-srivastava / @Jayesh) Amit Kumar (@hackeramitkumar / @Amit Kumar) Moshiur Rahman (@smoshiur1237 / @Moshiur Rahman) Pravar Agrawal (@pravarag / @pravarag) |