Re: [onap-tsc] Release Management Update

2019-01-03 Thread Stephen Terrill
Hi, Seasons greatings to all. Thank-you for your cooperation Gildas and I echo the words previously said. Best Regards, Steve. From: onap-tsc@lists.onap.org On Behalf Of GILBERT, MAZIN E (MAZIN E) Sent: Wednesday 2 January 2019 23:21 To: onap-tsc@lists.onap.org P Cc: onap-disc...@lists.ona

[onap-tsc] ONAP Release - TOSCA Requirements #Dublin

2019-01-03 Thread Catherine LEFEVRE
[cid:image002.jpg@01D4A2D5.63D34170] Good morning ONAP Architecture Team, TOSCA Task Force, Best wishes to you and to your family ! The ONAP TSC is currently working on the Dublin Release prioritization. Can you please provide some additional clarifications about the following TOSCA requirement

Re: [onap-tsc] Release Management Update

2019-01-03 Thread Catherine LEFEVRE
Dear Gildas, On behalf of the ONAP TSC, I want to thank you for your amazing contribution to the ONAP community since its inception. You have been instrumental to our ONAP Release success - coordinating with PTLs, tracking our milestone exit criteria, updating the ONAP TSC, following up on any

Re: [onap-tsc] Edge Coordinator Role Description

2019-01-03 Thread Catherine LEFEVRE
Good morning Ramki, My only comment is related to the role of Security in Edge Computing. Therefore I also would add: Concrete near-term & long-term recommendations (if any) and other inputs to ONAP Security Subcommittee. Best regards Catherine From: onap-tsc@lists.onap.org [mailto:onap-tsc@lis

Re: [onap-tsc] ONAP R3 Maintenance branch & cherry picking to R3 Branch

2019-01-03 Thread Catherine LEFEVRE
Good morning Viswa, Best wishes to you and to your family ! Concerning the Casablanca Maintenance Release, the scope (currently 66 items) has been defined as follows since December 10th, 2018. -ONLY Highest and High Priority bugs in Jira -Add Technical Debt (HTTPS Security, Upgra

Re: [E] Re: [onap-tsc] ONAP R3 Maintenance branch & cherry picking to R3 Branch

2019-01-03 Thread Viswanath Kumar Skand Priya via Lists.Onap.Org
Hi Catherine, Thanks for the clarification. I was under the assumption that, R3 maintenance release is actually "branched off" from R3 branch. Now I understand that's not the case. We simply allow the commits to original R3 branch and call it as maintenance release on Jan 31st. I reckon these comm

Re: [onap-tsc] Edge Coordinator Role Description

2019-01-03 Thread ramki krishnan
Dear Catherine, Many thanks for your feedback. I have incorporated your input in the Edge Coordinator Role Description below. Thanks, Ramki From: onap-tsc@lists.onap.org On Behalf Of Catherine LEFEVRE Sent: Thursday, January 3, 2019 6:41 PM To: onap-tsc@lists.onap.org Subject: Re: [onap-tsc]

Re: [E] [onap-tsc] ONAP R3 Maintenance branch & cherry picking to R3 Branch

2019-01-03 Thread Alexis de Talhouet
Viswa, Yes, this is correct. The release branch for R3 remain the same and Tags are created per Release, as well as version is bumped for individual artifacts (maven & docker). So basically, we will end up with the following after maintenance release: branch casablanca: tag 3.0.0 - ver

[onap-tsc] Please modify AAF Committer List

2019-01-03 Thread Jonathan Gathman
Please add SAI GANDHAM as AAF Committer (repositories authz, cadi, etc)   Sai has been working with AAF for some time (since Amsterdam), and understands the code and how to make changes safely.  He has been a good member of the AAF Team. Please remove VARUNESHWAR GUDISENA as AAF Committer   Varu

Re: [onap-tsc] Please modify AAF Committer List

2019-01-03 Thread Catherine LEFEVRE
Good morning Jonathan, Concerning Varun, Could you please open a Helpdesk ticket to LF (CC myself) in order to remove him as requested? Thank you Update the Resources and Repositories information accordingly: https://wiki.onap.org/display/DW/Resources+and+Repositories Concerning Sai, please fol