Various Akraino Release Upstream Dependencies and Compliance Table
As of R4R7, 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 each BP/Feature 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 R6 Requirement: (TO BE DISCUSSED in TSC)
- 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 R6 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 R4 (TBD)R7.
- Or an upstream fork is acceptable , but by BP, then the BP should lock the fork should be locked before R4 R6 release and the code should be merged back to upstream eventually.
Steps to update Upstream information by BP:
- 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.
R7 R4 Release Review Status (In Progress, all BPs please follow the schedule)
...