Release 5 BP/Feature Upstream Status
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.
Steps to update Upstream information:
Add an entry in the following table
Fill in the Upstream document field, typically the release note
Add detail upstream information into release notes, including the name of the upstream/releases. For example, Ubuntu/20.04. Please list all major upstreams the BP used.
R5 Release Review Status (In Progress, all BPs please follow the schedule)
Project Name | Upstream Documents (Provided by BP) | Review Date | Upstream Review Status (Edited by Upstream Subcommittee) | Comments (Any members) |
|---|---|---|---|---|
|
|
|
| |
| No changes from R4. Completed |
| ||
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) | Upstream Dependency Matrix and Upstream Project Information and ICN R5 Release Notes | 8/6/2021 | Completed |
|
Upstream Dependency Matrix and Upstream Project Information and ICN R5 Release Notes | 8/10/2021 | Completed |
| |
8/6/2021 | Completed |
| ||
8/6/2021 | Completed |
| ||
8/10/2021 | Completed | No changes from R4 | ||
|
|
|
| |
|
|
|
| |
|
|
|
| |
|
|
| ||
The AI Edge: Intelligent Vehicle-Infrastructure Cooperation System(I-VICS) |
|
|
| |
5G MEC/Slice System to Support Cloud Gaming, HD Video and Live Broadcasting Blueprint |
| Completed |
| |
|
|
|
| |
IEC Type 5: SmartNIC for Integrated Edge Cloud (IEC) Blueprint Family |
|
|
|
|
R5 - Architecture Documentation of Enterprise Applications on Lightweight 5G Telco Edge | 8/10/2021 | Completed |
| |
8/6/2021 | Completed |
| ||
8/10/2021 | Missing details | " dependencies of the release (upstream version, patches) still the same" Please link to the place where the same release information is provided. | ||
|
| Old updates. Need check if any update for R5 | ||
8/10/2021 | Completed | can improve with details of all upstream versions/releases | ||
8/10/2021 | Completed | No updates from R4 | ||
|
| Missing Details |
| |
| Completed | In the smart cities R5 release, there is only the security module parsec, which is an independent third-party open source project and does not depend on the existing Arkraino code repositories. | ||
| Missing details | Release 5 deliverables not found. | ||
| Missing Details | Updates are old in the upstream matrix. Need re-verification if any change in R5. No upstream information included in IEC Type 2 Release Notes for R5 | ||
8/25/2021 | Completed | Can be updated in the upstream Dependency matrix with the project name. Should we use the actual project name or blueprint family name in the "Project Name" Column | ||
10/14/2021 |
|
| ||
|
|
|