Release Upstream Compliance

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 Table (In Progress)

Project Name	Upstream Document	Upstream Completion Status	Comments
Connected Vehicle Blueprint
IEC Type 4: AR/VR oriented Edge Stack for Integrated Edge Cloud (IEC) Blueprint Family	Release Note-Type4	Same from R2. Completed
Micro-MEC	Release Notes for the MicroMEC Blueprint Release 3	No clear indication of the Upstream and versions
The AI Edge: School/Education Video Security Monitoring	Video Security Monitoring R3 Release Notes	No indication of the Upstream versions
5G MEC/Slice System to Support Cloud Gaming, HD Video and Live Broadcasting Blueprint	R3 - Release Notes	No indication of Upstream dependencies
IEC Type 5: SmartNIC for Integrated Edge Cloud (IEC) Blueprint Family	R3 Release Notes of IEC Type 3: Android cloud native applications on Arm servers in edge	No Upstream information
Enterprise Applications on Lightweight 5G Telco Edge	Upstream Dependency Matrix and Upstream Project Information	Completed	In Upstream Matrix Table
Radio Edge Cloud (REC)	Release 3	No Upstream information
ICN - Integrated Cloud-Native Family	ICN R3 Release Notes	Completed
ELIOT IoT Gateway Blueprint	ELIOT IoT Gateway Blueprint	No Upstream information
ELIOT SD-WAN/WAN Edge/uCPE Blueprint	ELIOT SD-WAN/WAN Edge/uCPE Blueprint	No Upstream information
Network Cloud and TF Integration Project	NC Family Documentation - Release 3	No Upstream information
KNI Provider access edge	KNI PAE Architecture document	Completed