Various Akraino Release Upstream Dependencies and Compliance Table


As of R4, in order to build a stable release (A release is a release which Downstream and Community can rebuild after a certain long period of time), Upstream will need to specify upstream repositories completely and with corresponding version/branch information. Also Upstream Sub-committee recommends to use tag instead of branch if possible.


R4 Requirement:


R4 Release Review Status (In Progress, all BPs please follow the schedule)



Project NameUpstream DocumentReview DateUpstream Completion StatusComments
Connected Vehicle Blueprint




IEC Type 4: AR/VR oriented Edge Stack for Integrated Edge Cloud (IEC) Blueprint FamilyRelease Note-Type4
Same from R2. Completed

Micro-MECRelease Notes for the MicroMEC Blueprint Release 3
No clear indication of the Upstream and versions

The AI Edge: School/Education Video Security MonitoringVideo Security Monitoring R3 Release Notes
No indication of the Upstream versions

5G MEC/Slice System to Support Cloud Gaming, HD Video and Live Broadcasting BlueprintR3 - Release Notes
No indication of Upstream dependencies

IEC Type 5: SmartNIC for Integrated Edge Cloud (IEC) Blueprint FamilyR3 Release Notes of IEC Type 3: Android cloud native applications on Arm servers in edge
No Upstream information

Enterprise Applications on Lightweight 5G Telco EdgeUpstream Dependency Matrix and Upstream Project Information
CompletedIn Upstream Matrix Table
Radio Edge Cloud (REC)Release 3
No Upstream information

ICN - Integrated Cloud-Native FamilyICN R3 Release Notes
Completed

ELIOT IoT Gateway BlueprintELIOT IoT Gateway Blueprint
No Upstream information

ELIOT SD-WAN/WAN Edge/uCPE BlueprintELIOT SD-WAN/WAN Edge/uCPE Blueprint
No Upstream information

Network Cloud and TF Integration ProjectNC Family Documentation - Release 3
No Upstream information

KNI Provider access edgeKNI PAE Architecture document
Completed