Versions Compared

Old Version 8

changes.mady.by.user Jim White

Saved on

compared with

New Version 9

changes.mady.by.user Jim White

Saved on

Key

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

...

  • DevOps Chairman is resigning.  New leadership is needed to guide this work group.  Over the course of the next couple of months, the current chair will hold review sessions during the working group meetings to educate more of the community or current systems and procedures and find a volunteer to guide and steer the direction of this important working group going forward.  The target is to identify a new leader by Christmas time 2018.
  • EdgeX Go code (inclusive of all development, build and test environments) will move to Go 1.11.
  • EdgeX Go code will use modules in place of Glide.
  • EdgeX will update to Consul 1.2.3 for Edinburgh.
  • Program artifacts (Go service executables, Java JAR files, etc.) will be retained and made available in Nexus.  This will allow 3rd parties to more easily reuse and package EdgeX for alternate deployments and to better support development efforts (not requiring all the services to be built all the time to work on a single service).

General Tasks and Notes

  • EdgeX has used Rocket Chat as the message channel for contributor and user information exchange since the project’s inception.  With the upcoming release, the community is going to switch to Slack – a more widely used and accepted form of developer communications.
  • With the Edinburgh release, the community has resolved to adopt a “Release Manager” to monitor, guide, document and manage each release.  The Release Manager role will rotate through organizations like Dell, IoTech, Intel, and Canonical.  Michael Hall will lead efforts to define the duties of the role and Keith Steele (or TSC chair) will coordinate the rotation of the role to the larger supporting organizations.
  • EdgeX will have and advertise its support contract/policy to the world with the Edinburgh release.
  • The TestQA and DevOps working groups will meet simultaneously in order to stream line efforts that are often intertwined.
  • A stretch goal for the Edinburgh release is something like a “12 factor apps” for how developers can build EdgeX services to better survive and operate in a distributed environment.  An additional stretch goal for Edinburgh would be to have a playground or test environment to test EdgeX service distribution.