...
- Add static artifact analysis into the EdgeX Jenkins Pipeline (analysis of Docker /runtime artifacts, not the source code)
- Add code and artifact signing with semantic versioning
- Conduct build performance optimizations by:
- Adding Pipelines for EdgeX Foundry base build images
- Allow basebuild images to be managed locally within Nexus
- Leverage PyPi Proxy for local pip dependencies
- Explore static code analysis like Codecov Coverity.io
General Tasks and Notes
- Move to Go 1.12 (evaluate and possibly move to Go 1.13 on its arrival)
- EdgeX will move from RAML to Swagger for API documentation
- Use nanoseconds for all Event/Reading timestamps (a change from milliseconds).
- Update the EdgeX "Offerings" page on the EdgeX Website to highlight 3rd parties offering EdgeX products and services.
- Research options for better building/packaging/using alternate infrastructure elements that would have been accomplished by Go Plugins if not for the fact that this Go Lang feature is not supported and apparently dying.
- Reconstitute the EdgeX marketing working group - lost with the LF Edge umbrella project creation. This working group will serve to meet EdgeX marketing needs (event planning, promotional material, etc.) as well as provide the LF Edge Marketing Group with EdgeX feedback and insure EdgeX marketing needs are satisfied.
- Capture unit, integration, and other testing coverage metrics so that the test coverage can be prepared at each face to face meeting. This will help address the need to implement a test coverage metric in the future.
- Elect a new release manager for Fuji and each subsequent release. In order to address pace of change issues, the release manager will attempt to implement release milestones like "no new functionality" dates.