Topics

EdgeX release 1.0.1

James.White2@...
 

TSC,

As of this morning, we have approval to release EdgeX 1.0.1 to fix a number of critical bugs – many of which are race condition related.  Additionally, some less critical scheduler, Snappy, and docs related items will go into this dot release as a target of opportunity.

 

WG Chairs, please confirm by End of Day 7/18 the following services will be tagged and artifacts released as part of 1.0.1:

Tag and generate release artifacts

Edgex-go

  • edgexfoundry/docker-core-config-seed-go:1.0.1
  • edgexfoundry/docker-export-client-go:1.0.1
  • edgexfoundry/docker-export-distro-go:1.0.1
  • edgexfoundry/docker-core-data-go:1.0.1
  • edgexfoundry/docker-core-metadata-go:1.0.1
  • edgexfoundry/docker-core-command-go:1.0.1
  • edgexfoundry/docker-support-logging-go:1.0.1
  • edgexfoundry/docker-support-notifications-go:1.0.1
  • edgexfoundry/docker-sys-mgmt-agent-go:1.0.1
  • edgexfoundry/docker-support-scheduler-go:1.0.1

Edgex-go-ARM

  • edgexfoundry/docker-core-config-seed-go-arm64:1.0.1
  • edgexfoundry/docker-export-client-go-arm64:1.0.1
  • edgexfoundry/docker-export-distro-go-arm64:1.0.1
  • edgexfoundry/docker-core-data-go-arm64:1.0.1
  • edgexfoundry/docker-core-metadata-go-arm64:1.0.1
  • edgexfoundry/docker-core-command-go-arm64:1.0.1
  • edgexfoundry/docker-support-logging-go-arm64:1.0.1
  • edgexfoundry/docker-support-notifications-go-arm64:1.0.1
  • edgexfoundry/docker-sys-mgmt-agent-go-arm64:1.0.1
  • edgexfoundry/docker-support-scheduler-go-arm64:1.0.1

Note:  because the issues do not affect or touch the Device Services (or SDK), Application Services (or SDK), security services or UIs, these artifacts do not need to be released and will stay at version 1.0.0.  If this assumption is incorrect, please advise ASAP.

 

Thanks,

Jim White

Director, IoT Platform Development Team & Distinguished Engineer

EdgeX Foundry Technical Steering Committee Vice Chairman

Dell Technologies | IoT Solutions Division

Office +1 512-723-6139, mobile/text +1 612-916-6693

james_white2@...

 

Iain Anderson
 



On 17/07/2019 18:42, James.White2@... wrote:

Note:  because the issues do not affect or touch the Device Services (or SDK), Application Services (or SDK), security services or UIs, these artifacts do not need to be released and will stay at version 1.0.0.  If this assumption is incorrect, please advise ASAP.



There have been a couple of small fixes on device-sdk-c since 1.0.0 so I'd be happy for this to take a 1.0.1

Regards,
Iain

James.White2@...
 

Iain – do we actually have artifacts released for the SDKs or device services yet?  I didn’t think we actually “released” anything for the SDKs and I thought the device services were going to be released Aug 1.

 

From: EdgeX-TSC@... <EdgeX-TSC@...> On Behalf Of Iain Anderson
Sent: Thursday, July 18, 2019 11:31 AM
To: EdgeX-TSC@...
Subject: Re: [Edgex-tsc] EdgeX release 1.0.1

 

[EXTERNAL EMAIL]

 

On 17/07/2019 18:42, James.White2@... wrote:

Note:  because the issues do not affect or touch the Device Services (or SDK), Application Services (or SDK), security services or UIs, these artifacts do not need to be released and will stay at version 1.0.0.  If this assumption is incorrect, please advise ASAP.

 


There have been a couple of small fixes on device-sdk-c since 1.0.0 so I'd be happy for this to take a 1.0.1

Regards,
Iain

Iain Anderson
 

You're right, I'll just put a 1.0.1 tag on at some point.

- Iain


On 18/07/2019 18:28, James.White2@... wrote:

Iain – do we actually have artifacts released for the SDKs or device services yet?  I didn’t think we actually “released” anything for the SDKs and I thought the device services were going to be released Aug 1.

 

From: EdgeX-TSC@... <EdgeX-TSC@...> On Behalf Of Iain Anderson
Sent: Thursday, July 18, 2019 11:31 AM
To: EdgeX-TSC@...
Subject: Re: [Edgex-tsc] EdgeX release 1.0.1

 

[EXTERNAL EMAIL]

 

On 17/07/2019 18:42, James.White2@... wrote:

Note:  because the issues do not affect or touch the Device Services (or SDK), Application Services (or SDK), security services or UIs, these artifacts do not need to be released and will stay at version 1.0.0.  If this assumption is incorrect, please advise ASAP.

 


There have been a couple of small fixes on device-sdk-c since 1.0.0 so I'd be happy for this to take a 1.0.1

Regards,
Iain