As of R5, in order to build a stable release, Upstream will need each BP/Feature to specify upstream repositories completely and with corresponding version/branch information.
R5 Requirement:
- If a BP has no code changes to upstream repositories, then it would just need to specify fully its upstream release versions in its release document, matching with its bluval testing versions.
- If a BP has code changes to upstream repositories, then it would need to either merge the code into the upstream before the R4 release time frame and updates its release versions. If the code cant be merged the code into upstream timely, then the BP will not fit into the R5.
- Or an upstream fork is acceptable, but the fork should be locked before R5 release and the code should be merged back to upstream eventually.
R5 Release Review Status (In Progress, all BPs please follow the schedule)
| Project Name | Upstream Documents | Review Date | Upstream Review Status (Edited by Upstream Subcommittee) | Comments |
|---|---|---|---|---|
| ICN - Integrated Cloud-Native Family | Upstream Dependency Matrix and Upstream Project Information and ICN R5 Release Notes | |||
| Connected Vehicle Blueprint(Aka CVB) | ||||
| IEC Type 4: AR/VR oriented Edge Stack for Integrated Edge Cloud (IEC) Blueprint Family | ||||
| Integrated Cloud Native NFV/App stack family (Short term: ICN) | ||||