...
- Release inclusion check
- IEC Type 1 and Type 2 were included in Akraino Release 1, 2 and 5
- IEC Type1&2 Release 1 Milestone Certification
- SW quality/functional check
- IEC does the blueprint validation tests daily. The validation daily job is at: https://jenkins.akraino.org/view/iec/job/bluval-daily-master/, and the log could be found at: https://nexus.akraino.org/content/sites/logs/enea/bluval_results/iec/master/;
- IEC has passed security scanning by a number of Open Source and proprietary tools used by Coala when committing the code everytime https://nexus.akraino.org/content/sites/logs/production/vex-yul-akraino-jenkins-prod-1/iec-tox-verify-master/
- Sonarcloud code check integrated in ci-management: https://sonarcloud.io/dashboard?id=iec
- HW definition check
- A reference platform is documented in detail for the IEC Validation Lab with 2 labs (Enea lab and Arm lab).
- Additional hardware information for non-reference platforms is available in the IEC Hardware Requirement and blueprint species of Type1 and Type2.
- Upstream dependency check
- The upstream dependencies are enumerated in non-machine-readable form on the wiki: IEC Type1&2 Release Notes for R2#SoftwareVersion and in machine readable form in the Gerrit repos as described in IEC Gerrit and Code Repository Overview
- Documentation check
- Documentation was created for Akraino Release 1 documentation and Release 2 documentation and some minor updates have been made but we are not aware of any significant documentation issues
- Community Health and Stability check
- Meetings are held weekly and minutes are published with a list of attendees: IEC Meetings
- Meeting content includes welcoming new participants and providing introduction to the projects as well as discussing ongoing progress
- Contributions from ENEA are working on adding CentOS support to the previously ubuntu-only code , providing validation lab for Arkaino Jenkins IEC jobs