...
| Milestone | Date | Deliverable | Notes |
|---|---|---|---|
| Dev1 Start |
| Vetted Jira list for the EarlyDrop (ED) | List of planned jiras for the development sprint (M1) |
| M1 checkpoint |
| TSC reviews and sign-off on intended El Alto Content | Content defined by fixVersion = "El Alto Release" Early Drop content defined by: label contains "El_Alto_Early_Drop" |
| Test Plan Review |
| Early drop and Final release test plan review and sign off by TSC | |
| Test1 Start |
| Test to deliver ED | Phased integration and test plan. (M4_early_drop) Run daily sanity on El Alto released images, and start vFW, vLB and vCPE use case testing All containers for ED are due to be delivered to testing/integration |
| Dev1 End |
| Priority 0 vulnerabilities addressed | List of completed jiras due API documentation complete Arch changes reviewed and documented |
| Dev2 Start |
| Fixes only to support ED | Integration team drives bug list priority. All other development deferred check in until Dev3 Integration will work with dev teams to close highest/high priority jiras discovered during integration test. All integration tests should be finished three days before ED release so we will have time to update release note, put tag on branches, etc. |
| Dev2 End |
| ED released | Complete release - includes rel_notes, named release, branch. (M2/M3 milestone) |
| Test1 End |
| ED released | Complete release - includes rel_notes, named release, branch. (Sign_off_early_drop) |
| EarlyDrop |
| ||
| Dev3 Start |
| ||
| Test2 Start |
| ||
| Dev3 End |
| All code complete (M4) | |
| Test2 End |
| ||
| Test3 Start |
| Pair-wise testing (1 wk only) and Integration (RC0) All containers due to be delivered to testing/integration | |
| Test3 End |
| ||
| El Alto Release |
|
...