Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

As of R7, in order to build a stable release, Upstream will need each BP/Feature to specify upstream repositories completely and with corresponding version/branch information.


R6 R7 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 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 R7.
  • Or an upstream fork is acceptable by BP, then the BP should lock the fork before R6 release and the code should be merged back to upstream eventually.

...

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



No.Project NameUpstream DocumentReview DateUpstream Completion StatusComments
28

Smart Data Transaction for CPS

Colin Peters 

Smart Data Transaction for CPS R7 Release Notes

Dependencies listed in Release Content

1/18Approved.

29

Robot basic architecture based on SSES

Fukano Haruhisa

Release Notes for release7

Refer to release content.

12/20Approved


CFN (Computing Force Network) Ubiquitous Computing Force Scheduling

R7 Release Notes - Akraino - Akraino Confluence

Refer to release content.