...
- 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)
Missing Upstream information
8/6/2021 | Completed | |||
The AI Edge: Federated ML application at edge | R5 Federated ML application at edge Release Notes | 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. |
KubeEdge Edge Service Blueprint | KubeEdge BP Release Notes | Old updates. Need check if any update for R5 | ||
Kubernetes Native Infrastructure (KNI) Blueprint Family | Upstream Dependency Matrix and Upstream Project Information | 8/10/2021 | Completed | can improve with details of all upstream versions/releases |
Private LTE/5G ICN Blueprint | Upstream Dependency Matrix and Upstream Project Information | 8/10/2021 | Completed | No updates from R4 |
Rural Edge blueprint for Tami COVID-19 Blueprint Family | Missing Details | |||
Smart Cities | Smart Cities R5 Upstream | 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. | |
MEC-based Stable Topology Prediction for Vehicular Networks | Missing details | Release 5 deliverables not found. | ||
IEC Type 2 for Integrated Edge Cloud (IEC) Blueprint Family | Upstream Dependency Matrix and Upstream Project Information | 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 | |
IIoT at the Smart Device Edge (family) | IIoT Predictive Maintenance Release Notes | 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 |
Federated Multi-Access Edge Cloud Platform | R5 Release Notes | 10/14/2021 | ||
Smart Data Transaction for CPS | R6 Release Notes |