This page tracks release information for FD.io CSIT-2106. It is updated regularly by hand. Real-time information is available in FD.io CSIT code repository and auto-generated docs.
|F0||TBD||Test case keywords code complete. Only low-risk changes accepted.|
|RC1||TBD (F0+7)||Code complete. Pull first release branch. Only bug fixes, infra changes and framework optimizations are accepted in release branch. Date aligned with VPP RC1. Start dry-runs to identify CSIT gaps on less frequently run tests.|
|RC2||TBD (RC1+28)||Dry-run testing begins of VPP RC2, performance and functional. Date aligned with VPP RC2.|
|CSIT Release||TBD (RC2+7)||CSIT release complete. VPP release testing starts. Date aligned with VPP Formal Release. Only critical changes (as they usually require re-starting release testing) or changes not affecting results (such as documentation improvements) are accepted in release branch. Release testing also includes testing previous VPP version with new CSIT code, needed for comparison tables.|
|Report Publish||TBD (RC2+14)||CSIT report published for VPP release. On master branch, start replacing (or dropping support for) APIs deprecated in the newly released VPP version (as we do not need to run the previous VPP version with newest CSIT code from now on).|
Jira Task Tracking
All CSIT release deliverables should be tracked in FDio CSIT Jira using one of the following Jira Epic categories:
Multi-Release Work Areas
- No known external dependencies.