Date   
EdgeX TSC DevOps and QA/Test WG Meeting (Weekly) - Thu, 04/18/2019 7:00am-8:00am #cal-reminder

EdgeX-TSC-DevOps@lists.edgexfoundry.org Calendar <EdgeX-TSC-DevOps@...>
 

Reminder:
EdgeX TSC DevOps and QA/Test WG Meeting (Weekly)

When:
Thursday, 18 April 2019
7:00am to 8:00am
(GMT-07:00) America/Los Angeles

Where:
https://zoom.us/j/967227826

Organizer:
EdgeX-TSC-DevOps@...

Description:
EdgeX TSC DevOps and QA/Test WG Meeting. Meeting content posted to DevOps Wiki.
Meeting Lead: James Gregg, EdgeX DevOps WG Chair, james.r.gregg@...
-----
Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/967227826

Or iPhone one-tap :
    US: +16465588656,,967227826# or +16699006833,,967227826# 
Or Telephone:
    Dial(for higher quality, dial a number based on your current location): 
        US: +1 646 558 8656 or +1 669 900 6833 or +1 855 880 1246 (Toll Free) or +1 877 369 0926 (Toll Free)
    Meeting ID: 967 227 826
    International numbers available: https://zoom.us/u/bmaYSxofb

An RSVP is requested. Click here to RSVP

EdgeX TSC DevOps and QA/Test WG Meeting (Weekly) - Thu, 04/25/2019 7:00am-8:00am #cal-reminder

EdgeX-TSC-DevOps@lists.edgexfoundry.org Calendar <EdgeX-TSC-DevOps@...>
 

Reminder:
EdgeX TSC DevOps and QA/Test WG Meeting (Weekly)

When:
Thursday, 25 April 2019
7:00am to 8:00am
(GMT-07:00) America/Los Angeles

Where:
https://zoom.us/j/967227826

Organizer:
EdgeX-TSC-DevOps@...

Description:
EdgeX TSC DevOps and QA/Test WG Meeting. Meeting content posted to DevOps Wiki.
Meeting Lead: James Gregg, EdgeX DevOps WG Chair, james.r.gregg@...
-----
Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/967227826

Or iPhone one-tap :
    US: +16465588656,,967227826# or +16699006833,,967227826# 
Or Telephone:
    Dial(for higher quality, dial a number based on your current location): 
        US: +1 646 558 8656 or +1 669 900 6833 or +1 855 880 1246 (Toll Free) or +1 877 369 0926 (Toll Free)
    Meeting ID: 967 227 826
    International numbers available: https://zoom.us/u/bmaYSxofb

An RSVP is requested. Click here to RSVP

Cancelled Event: EdgeX TSC DevOps and QA/Test WG Meeting (Weekly) - Thursday, 9 May 2019 #cal-cancelled

EdgeX-TSC-DevOps@lists.edgexfoundry.org Calendar <EdgeX-TSC-DevOps@...>
 

Cancelled: EdgeX TSC DevOps and QA/Test WG Meeting (Weekly)

This event has been cancelled.

When:
Thursday, 9 May 2019
7:00am to 8:00am
(GMT-07:00) America/Los Angeles

Where:
https://zoom.us/j/967227826

Organizer:
EdgeX-TSC-DevOps@...

Description:
EdgeX TSC DevOps and QA/Test WG Meeting. Meeting content posted to DevOps Wiki.
Meeting Lead: James Gregg, EdgeX DevOps WG Chair, james.r.gregg@...
-----
Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/967227826

Or iPhone one-tap :
    US: +16465588656,,967227826# or +16699006833,,967227826# 
Or Telephone:
    Dial(for higher quality, dial a number based on your current location): 
        US: +1 646 558 8656 or +1 669 900 6833 or +1 855 880 1246 (Toll Free) or +1 877 369 0926 (Toll Free)
    Meeting ID: 967 227 826
    International numbers available: https://zoom.us/u/bmaYSxofb

EdgeX DevOps WG meeting 5/9/2019 cancelled

Gregg, James R
 

I’m on vacation this week so there will not be a EdgeX DevOps WG meeting this week. 

 

James Gregg

IOTG RBHE DevOps | EdgeX Foundry DevOps

Email: james.r.gregg@...

Tel: (480) 552-7965

 

Upcoming Event: EdgeX TSC DevOps and QA/Test WG Meeting (Weekly) - Thu, 05/16/2019 7:00am-8:00am, Please RSVP #cal-reminder

EdgeX-TSC-DevOps@lists.edgexfoundry.org Calendar <EdgeX-TSC-DevOps@...>
 

Reminder: EdgeX TSC DevOps and QA/Test WG Meeting (Weekly)

When: Thursday, 16 May 2019, 7:00am to 8:00am, (GMT-07:00) America/Los Angeles

Where:https://zoom.us/j/967227826

An RSVP is requested. Click here to RSVP

Organizer: EdgeX-TSC-DevOps@...

Description: EdgeX TSC DevOps and QA/Test WG Meeting. Meeting content posted to DevOps Wiki.
Meeting Lead: James Gregg, EdgeX DevOps WG Chair, james.r.gregg@...
-----
Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/967227826

Or iPhone one-tap :
    US: +16465588656,,967227826# or +16699006833,,967227826# 
Or Telephone:
    Dial(for higher quality, dial a number based on your current location): 
        US: +1 646 558 8656 or +1 669 900 6833 or +1 855 880 1246 (Toll Free) or +1 877 369 0926 (Toll Free)
    Meeting ID: 967 227 826
    International numbers available: https://zoom.us/u/bmaYSxofb

Upcoming Event: EdgeX TSC DevOps and QA/Test WG Meeting (Weekly) - Thu, 05/23/2019 7:00am-8:00am, Please RSVP #cal-reminder

EdgeX-TSC-DevOps@lists.edgexfoundry.org Calendar <EdgeX-TSC-DevOps@...>
 

Reminder: EdgeX TSC DevOps and QA/Test WG Meeting (Weekly)

When: Thursday, 23 May 2019, 7:00am to 8:00am, (GMT-07:00) America/Los Angeles

Where:https://zoom.us/j/967227826

An RSVP is requested. Click here to RSVP

Organizer: EdgeX-TSC-DevOps@...

Description: EdgeX TSC DevOps and QA/Test WG Meeting. Meeting content posted to DevOps Wiki.
Meeting Lead: James Gregg, EdgeX DevOps WG Chair, james.r.gregg@...
-----
Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/967227826

Or iPhone one-tap :
    US: +16465588656,,967227826# or +16699006833,,967227826# 
Or Telephone:
    Dial(for higher quality, dial a number based on your current location): 
        US: +1 646 558 8656 or +1 669 900 6833 or +1 855 880 1246 (Toll Free) or +1 877 369 0926 (Toll Free)
    Meeting ID: 967 227 826
    International numbers available: https://zoom.us/u/bmaYSxofb

Upcoming Event: EdgeX TSC DevOps and QA/Test WG Meeting (Weekly) - Thu, 05/30/2019 7:00am-8:00am, Please RSVP #cal-reminder

EdgeX-TSC-DevOps@lists.edgexfoundry.org Calendar <EdgeX-TSC-DevOps@...>
 

Reminder: EdgeX TSC DevOps and QA/Test WG Meeting (Weekly)

When: Thursday, 30 May 2019, 7:00am to 8:00am, (GMT-07:00) America/Los Angeles

Where:https://zoom.us/j/967227826

An RSVP is requested. Click here to RSVP

Organizer: EdgeX-TSC-DevOps@...

Description: EdgeX TSC DevOps and QA/Test WG Meeting. Meeting content posted to DevOps Wiki.
Meeting Lead: James Gregg, EdgeX DevOps WG Chair, james.r.gregg@...
-----
Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/967227826

Or iPhone one-tap :
    US: +16465588656,,967227826# or +16699006833,,967227826# 
Or Telephone:
    Dial(for higher quality, dial a number based on your current location): 
        US: +1 646 558 8656 or +1 669 900 6833 or +1 855 880 1246 (Toll Free) or +1 877 369 0926 (Toll Free)
    Meeting ID: 967 227 826
    International numbers available: https://zoom.us/u/bmaYSxofb

Upcoming Event: EdgeX TSC DevOps and QA/Test WG Meeting (Weekly) - Thu, 06/06/2019 7:00am-8:00am, Please RSVP #cal-reminder

EdgeX-TSC-DevOps@lists.edgexfoundry.org Calendar <EdgeX-TSC-DevOps@...>
 

Reminder: EdgeX TSC DevOps and QA/Test WG Meeting (Weekly)

When: Thursday, 6 June 2019, 7:00am to 8:00am, (GMT-07:00) America/Los Angeles

Where:https://zoom.us/j/967227826

An RSVP is requested. Click here to RSVP

Organizer: EdgeX-TSC-DevOps@...

Description: EdgeX TSC DevOps and QA/Test WG Meeting. Meeting content posted to DevOps Wiki.
Meeting Lead: James Gregg, EdgeX DevOps WG Chair, james.r.gregg@...
-----
Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/967227826

Or iPhone one-tap :
    US: +16465588656,,967227826# or +16699006833,,967227826# 
Or Telephone:
    Dial(for higher quality, dial a number based on your current location): 
        US: +1 646 558 8656 or +1 669 900 6833 or +1 855 880 1246 (Toll Free) or +1 877 369 0926 (Toll Free)
    Meeting ID: 967 227 826
    International numbers available: https://zoom.us/u/bmaYSxofb

edinburgh release asks

Jacob Blain Christen (Intel)
 

All,

 

Lisa and I put together the asks from this morning’s DevOps call

 

http://gist.github.com/dweomer/550d3740c0ebf5f2b4231a8d5b439a4f

 

-- 

Jacob Blain Christen

IOTG / RSD DevOps / Sr. DevOps Engineer

E: jacob.blain.christen@...

M: 480-779-7443

 

Re: edinburgh release asks

Ian Johnson
 

Hi Jacob,

Thanks for putting this together. I do have one consideration with respect to not cutting a new branch for i.e. device-snmp-go for the snap jobs. If we don't cut the branch then I think that means we should also not request snap tracks for those repos until as you say they break compatibility, and as such also not create additional Edinburgh branch snap jobs.

I think this is all fine, but we should document somewhere that when a branch for Edinburgh is cut, in addition to the normal jobs snap jobs will also need to be created. I raise this issue because right now it seems that I'm the only one creating these snap jobs and it's easy for me to do so during a release when we're talking about all of the repos, but when this branch gets cut at some later date me or whoever else is helping maintain snaps may not be looped into that decision. 

Is there somewhere we have documented specific EdgeX release processes? If we have that then I can document there how to create the snap jobs (it's all already templated so it's quite easy to create the new yaml in ci-management) and that should help ensure whoever works on this when a future release is cut out of sync with the normal release creates the new snap jobs.

Thanks,
Ian


On Thu, Jun 6, 2019, 17:44 Jacob Blain Christen (Intel) <jacob.blain.christen@...> wrote:

All,

 

Lisa and I put together the asks from this morning’s DevOps call

 

http://gist.github.com/dweomer/550d3740c0ebf5f2b4231a8d5b439a4f

 

-- 

Jacob Blain Christen

IOTG / RSD DevOps / Sr. DevOps Engineer

E: jacob.blain.christen@...

M: 480-779-7443

 

Re: edinburgh release asks

Gregg, James R
 

Ian,

Here’s the direct link to the release process as documented.

https://wiki.edgexfoundry.org/display/FA/Release+Process

 

 

~ James Gregg

 

From: EdgeX-TSC-DevOps@... <EdgeX-TSC-DevOps@...> On Behalf Of Ian Johnson
Sent: Thursday, June 6, 2019 4:15 PM
To: Blain Christen, Jacob <jacob.blain.christen@...>
Cc: EdgeX-TSC-DevOps@...
Subject: Re: [Edgex-tsc-devops] edinburgh release asks

 

Hi Jacob,

 

Thanks for putting this together. I do have one consideration with respect to not cutting a new branch for i.e. device-snmp-go for the snap jobs. If we don't cut the branch then I think that means we should also not request snap tracks for those repos until as you say they break compatibility, and as such also not create additional Edinburgh branch snap jobs.

 

I think this is all fine, but we should document somewhere that when a branch for Edinburgh is cut, in addition to the normal jobs snap jobs will also need to be created. I raise this issue because right now it seems that I'm the only one creating these snap jobs and it's easy for me to do so during a release when we're talking about all of the repos, but when this branch gets cut at some later date me or whoever else is helping maintain snaps may not be looped into that decision. 

 

Is there somewhere we have documented specific EdgeX release processes? If we have that then I can document there how to create the snap jobs (it's all already templated so it's quite easy to create the new yaml in ci-management) and that should help ensure whoever works on this when a future release is cut out of sync with the normal release creates the new snap jobs.

 

Thanks,

Ian

On Thu, Jun 6, 2019, 17:44 Jacob Blain Christen (Intel) <jacob.blain.christen@...> wrote:

All,

 

Lisa and I put together the asks from this morning’s DevOps call

 

http://gist.github.com/dweomer/550d3740c0ebf5f2b4231a8d5b439a4f

 

-- 

Jacob Blain Christen

IOTG / RSD DevOps / Sr. DevOps Engineer

E: jacob.blain.christen@...

M: 480-779-7443

 

Re: edinburgh release asks

James.White2@...
 

Thanks for pulling this together Jacob.

 

On the first part, I don’t see the Pipeline Repos ask as too big a deal, but I am still unclear as to why this is desired.  Are you suggesting we not make Edinburgh branches until they are actually needed?  We did cut branches on all the other repositories.  Would it have been your advocation not to cut those branches as well until necessary?

 

On the second issue – device-sdk-go release – I’d ask that this be covered and debated in the device service WG for Monday of next week.  Steve Osselton, can you add this to the agenda?

 

Thanks

Jim

 

From: EdgeX-TSC-DevOps@... <EdgeX-TSC-DevOps@...> On Behalf Of Jacob Blain Christen (Intel)
Sent: Thursday, June 6, 2019 5:44 PM
To: EdgeX-TSC-DevOps@...
Subject: [Edgex-tsc-devops] edinburgh release asks

 

[EXTERNAL EMAIL]

All,

 

Lisa and I put together the asks from this morning’s DevOps call

 

http://gist.github.com/dweomer/550d3740c0ebf5f2b4231a8d5b439a4f

 

-- 

Jacob Blain Christen

IOTG / RSD DevOps / Sr. DevOps Engineer

E: jacob.blain.christen@...

M: 480-779-7443

 

Re: edinburgh release asks

Rashidi-ranjbar, Lisa A
 

Hi Jim,

 

To be clear we are advocating that the Edinburgh branches are not needed right away in the pipeline enabled repos.

This is because with the pipeline jobs we have the ability to do a release off the master branch.

For the freestyle jobs creating the branch is needed because we do not have a mechanism to release off master.

In the event that a pipeline repo has a non-backwards compatible change we can create the Edinburgh branch at that time.

 

This is why we are suggesting to move device-sdk-go to a pipeline job. We can make release candidates off the master branch for device-sdk-go which will allow for more integration time.

I can go through more implications in the device WG next week.

 

To clarify for Edinburgh we only expected to have the go-modules with pipeline enabled jobs.

Since we got a little bit ahead we started to work on Fuji scope in DevOps.

These discussions about releasing off master I originally thought would happen after Edinburgh was over.

Since we have 2 extra repos with pipelines enabled now – we need have this discussion and to start communicating the pros and cons more.

 

Thanks,

Lisa

 

From: EdgeX-TSC-DevOps@... <EdgeX-TSC-DevOps@...> On Behalf Of James.White2@...
Sent: Thursday, June 6, 2019 7:18 PM
To: Blain Christen, Jacob <jacob.blain.christen@...>; EdgeX-TSC-DevOps@...
Subject: Re: [Edgex-tsc-devops] edinburgh release asks

 

Thanks for pulling this together Jacob.

 

On the first part, I don’t see the Pipeline Repos ask as too big a deal, but I am still unclear as to why this is desired.  Are you suggesting we not make Edinburgh branches until they are actually needed?  We did cut branches on all the other repositories.  Would it have been your advocation not to cut those branches as well until necessary?

 

On the second issue – device-sdk-go release – I’d ask that this be covered and debated in the device service WG for Monday of next week.  Steve Osselton, can you add this to the agenda?

 

Thanks

Jim

 

From: EdgeX-TSC-DevOps@... <EdgeX-TSC-DevOps@...> On Behalf Of Jacob Blain Christen (Intel)
Sent: Thursday, June 6, 2019 5:44 PM
To:
EdgeX-TSC-DevOps@...
Subject: [Edgex-tsc-devops] edinburgh release asks

 

[EXTERNAL EMAIL]

All,

 

Lisa and I put together the asks from this morning’s DevOps call

 

http://gist.github.com/dweomer/550d3740c0ebf5f2b4231a8d5b439a4f

 

-- 

Jacob Blain Christen

IOTG / RSD DevOps / Sr. DevOps Engineer

E: jacob.blain.christen@...

M: 480-779-7443

 

Re: edinburgh release asks

James.White2@...
 

OK – so we will wait for the next DevOps call to take any action and can discuss.

 

If you think we need to act sooner, please advise so we can try to hash things out by email or have a separate call.

Jim

 

From: Rashidi-ranjbar, Lisa A <lisa.a.rashidi-ranjbar@...>
Sent: Friday, June 7, 2019 11:27 AM
To: White2, James; Blain Christen, Jacob; EdgeX-TSC-DevOps@...
Subject: RE: [Edgex-tsc-devops] edinburgh release asks

 

[EXTERNAL EMAIL]

Hi Jim,

 

To be clear we are advocating that the Edinburgh branches are not needed right away in the pipeline enabled repos.

This is because with the pipeline jobs we have the ability to do a release off the master branch.

For the freestyle jobs creating the branch is needed because we do not have a mechanism to release off master.

In the event that a pipeline repo has a non-backwards compatible change we can create the Edinburgh branch at that time.

 

This is why we are suggesting to move device-sdk-go to a pipeline job. We can make release candidates off the master branch for device-sdk-go which will allow for more integration time.

I can go through more implications in the device WG next week.

 

To clarify for Edinburgh we only expected to have the go-modules with pipeline enabled jobs.

Since we got a little bit ahead we started to work on Fuji scope in DevOps.

These discussions about releasing off master I originally thought would happen after Edinburgh was over.

Since we have 2 extra repos with pipelines enabled now – we need have this discussion and to start communicating the pros and cons more.

 

Thanks,

Lisa

 

From: EdgeX-TSC-DevOps@... <EdgeX-TSC-DevOps@...> On Behalf Of James.White2@...
Sent: Thursday, June 6, 2019 7:18 PM
To: Blain Christen, Jacob <jacob.blain.christen@...>; EdgeX-TSC-DevOps@...
Subject: Re: [Edgex-tsc-devops] edinburgh release asks

 

Thanks for pulling this together Jacob.

 

On the first part, I don’t see the Pipeline Repos ask as too big a deal, but I am still unclear as to why this is desired.  Are you suggesting we not make Edinburgh branches until they are actually needed?  We did cut branches on all the other repositories.  Would it have been your advocation not to cut those branches as well until necessary?

 

On the second issue – device-sdk-go release – I’d ask that this be covered and debated in the device service WG for Monday of next week.  Steve Osselton, can you add this to the agenda?

 

Thanks

Jim

 

From: EdgeX-TSC-DevOps@... <EdgeX-TSC-DevOps@...> On Behalf Of Jacob Blain Christen (Intel)
Sent: Thursday, June 6, 2019 5:44 PM
To:
EdgeX-TSC-DevOps@...
Subject: [Edgex-tsc-devops] edinburgh release asks

 

[EXTERNAL EMAIL]

All,

 

Lisa and I put together the asks from this morning’s DevOps call

 

http://gist.github.com/dweomer/550d3740c0ebf5f2b4231a8d5b439a4f

 

-- 

Jacob Blain Christen

IOTG / RSD DevOps / Sr. DevOps Engineer

E: jacob.blain.christen@...

M: 480-779-7443

 

Upcoming Event: EdgeX TSC DevOps and QA/Test WG Meeting (Weekly) - Thu, 06/13/2019 7:00am-8:00am, Please RSVP #cal-reminder

EdgeX-TSC-DevOps@lists.edgexfoundry.org Calendar <EdgeX-TSC-DevOps@...>
 

Reminder: EdgeX TSC DevOps and QA/Test WG Meeting (Weekly)

When: Thursday, 13 June 2019, 7:00am to 8:00am, (GMT-07:00) America/Los Angeles

Where:https://zoom.us/j/967227826

An RSVP is requested. Click here to RSVP

Organizer: EdgeX-TSC-DevOps@...

Description: EdgeX TSC DevOps and QA/Test WG Meeting. Meeting content posted to DevOps Wiki.
Meeting Lead: James Gregg, EdgeX DevOps WG Chair, james.r.gregg@...
-----
Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/967227826

Or iPhone one-tap :
    US: +16465588656,,967227826# or +16699006833,,967227826# 
Or Telephone:
    Dial(for higher quality, dial a number based on your current location): 
        US: +1 646 558 8656 or +1 669 900 6833 or +1 855 880 1246 (Toll Free) or +1 877 369 0926 (Toll Free)
    Meeting ID: 967 227 826
    International numbers available: https://zoom.us/u/bmaYSxofb

LF: Service Desk Migration (Update to helpdesk@)

Brett Preston
 

Hi,

The Linux Foundation IT team is migrating from an email-based support system (or as you may be familiar with it: helpdesk@project), which had used Request Tracker, to a web-based platform provided by Jira Service Desk. We are doing this in order to improve our level of service and your support experience.

The following are the primary improvements you should expect after migration is complete:
  1. Single Sign-On with other Linux Foundation sites, using the same LF ID credentials
  2. Integration with knowledge base articles to help identify possible self-service solutions
  3. Ability to track all your support requests across various Projects via the same service desk interface
  4. Ability to see public issues created by other members of your Project
The new service desk will become available to you starting Monday, June 17, 2019.

Any support requests that are already open in RT (through helpdesk@project) will be preserved and completed there, so there is no need to re-submit them again using the Jira Service Desk.

Any new tickets created in RT (through helpdesk@project) will be automatically closed with a suggestion and instruction to use the new service desk procedure.

Starting Monday, June 17 - please use the procedure described in the attached "Getting LF IT Help" document.

Thank you,


Brett

--
Brett Preston
Sr. Program Manager
The Linux Foundation
+1 (971) 303-9030

Upcoming Event: EdgeX TSC DevOps and QA/Test WG Meeting (Weekly) - Thu, 06/20/2019 7:00am-8:00am, Please RSVP #cal-reminder

EdgeX-TSC-DevOps@lists.edgexfoundry.org Calendar <EdgeX-TSC-DevOps@...>
 

Reminder: EdgeX TSC DevOps and QA/Test WG Meeting (Weekly)

When: Thursday, 20 June 2019, 7:00am to 8:00am, (GMT-07:00) America/Los Angeles

Where:https://zoom.us/j/967227826

An RSVP is requested. Click here to RSVP

Organizer: EdgeX-TSC-DevOps@...

Description: EdgeX TSC DevOps and QA/Test WG Meeting. Meeting content posted to DevOps Wiki.
Meeting Lead: James Gregg, EdgeX DevOps WG Chair, james.r.gregg@...
-----
Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/967227826

Or iPhone one-tap :
    US: +16465588656,,967227826# or +16699006833,,967227826# 
Or Telephone:
    Dial(for higher quality, dial a number based on your current location): 
        US: +1 646 558 8656 or +1 669 900 6833 or +1 855 880 1246 (Toll Free) or +1 877 369 0926 (Toll Free)
    Meeting ID: 967 227 826
    International numbers available: https://zoom.us/u/bmaYSxofb

Updated Event: EdgeX TSC DevOps WG Meeting (Weekly) #cal-invite

EdgeX-TSC-DevOps@lists.edgexfoundry.org Calendar <EdgeX-TSC-DevOps@...>
 

EdgeX TSC DevOps WG Meeting (Weekly)

When:
Thursday, 17 January 2019
7:00am to 8:00am
(GMT-08:00) America/Los Angeles
Repeats: Weekly on Thursday

Where:
https://zoom.us/j/967227826

Organizer:
EdgeX-TSC-DevOps@...

An RSVP is requested. Click here to RSVP

Description:
EdgeX TSC DevOps and QA/Test WG Meeting. Meeting content posted to DevOps Wiki.
Meeting Lead: James Gregg, EdgeX DevOps WG Chair, james.r.gregg@...
-----
Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/967227826

Or iPhone one-tap :
    US: +16465588656,,967227826# or +16699006833,,967227826# 
Or Telephone:
    Dial(for higher quality, dial a number based on your current location): 
        US: +1 646 558 8656 or +1 669 900 6833 or +1 855 880 1246 (Toll Free) or +1 877 369 0926 (Toll Free)
    Meeting ID: 967 227 826
    International numbers available: https://zoom.us/u/bmaYSxofb

release tag issue of edinburgh

Cloud Tsai <cloud@...>
 

Hi all,

I noticed a issue of the release tag.  It is caused by Go Module limitation.
We have tagged 1.0.0 for most of the repository now, but we should tag "v1.0.0" for Go Module recognition.  

It should be the same as what we did in go-mod-core-contracts. 

It is fine for the most of repositories, but device-sdk-go needs the character "v" for other Device Services.  Also, it would be better to have this consistence on all the repositories.

By the way, James and DevOps team, I need additional help for the Device Services.
We need to release device-sdk-go first, and then merge the following PRs before releasing other Device Services to make them depend on device-sdk-go v1.0.0.  Thank you.

 

--
Best Regards,
Cloud Tsai

Re: release tag issue of edinburgh

Eric Ball
 

All tags have been changed to "v<version>" for the edinburgh release.


On Tue, Jun 25, 2019 at 12:27 AM Cloud Tsai <cloud@...> wrote:
Hi all,

I noticed a issue of the release tag.  It is caused by Go Module limitation.
We have tagged 1.0.0 for most of the repository now, but we should tag "v1.0.0" for Go Module recognition.  

It should be the same as what we did in go-mod-core-contracts. 

It is fine for the most of repositories, but device-sdk-go needs the character "v" for other Device Services.  Also, it would be better to have this consistence on all the repositories.

By the way, James and DevOps team, I need additional help for the Device Services.
We need to release device-sdk-go first, and then merge the following PRs before releasing other Device Services to make them depend on device-sdk-go v1.0.0.  Thank you.

 

--
Best Regards,
Cloud Tsai