We depend on modeling subcommittees to review and archive our models, but not 
modeling/etsicatalog project.

 Therefore, in the requirement description,  I think we can change it to 
depends on modeling Subcommittee. Is this feasible?

Best regards,
Keguang



[email protected]
 
From: denghui (L) via lists.onap.org
Date: 2022-07-21 16:43
To: [email protected]; [email protected]; dmcbride
CC: [email protected].; 'onap-release'; Lefevre, Catherine; 
[email protected]; 'denglingli'; yangxu (H)
Subject: Re: [Onap-release] Modeling/etsicatalog withdraw form Kohn release
Thanks Keguang and yuanhong for quick response, in this case, shall we remove 
modeling dependency in REQ 1267?
 
Best regards,
DEGN Hui
 
From: [email protected] [mailto:[email protected]] 
Sent: Thursday, July 21, 2022 3:07 PM
To: [email protected]; dmcbride <[email protected]>; 
denghui (L) <[email protected]>
Cc: [email protected]. <[email protected]>; 'onap-release' 
<[email protected]>; Lefevre, Catherine 
<[email protected]>; [email protected]; 'denglingli' 
<[email protected]>; yangxu (H) <[email protected]>
Subject: Re: RE: Modeling/etsicatalog withdraw form Kohn release
 
Hi David,
 
As Yuanhong said, our models only need to be archived in modeling, and do not 
rely on the modeling/etsicatalog project.
 
Best regards,
Keguang
 


[email protected]
 
From: dengyuanhong
Date: 2022-07-21 15:02
To: 'David McBride'; 'denghui \(L\)'; [email protected]
CC: [email protected]; 'onap-release'; 'Catherine LEFEVRE'; 'Kenny Paul'; 
'邓灵莉'; 'yangxu \(H\)'
Subject: RE: Modeling/etsicatalog withdraw form Kohn release
Hi David,
 
I have already contacted with Keguang, REQ-1267 does not depend on the 
modeling/etsicatalog project, it only has a relationship with the Modeling 
Committee.
 
Best regards,
Yuanhong
 
From: David McBride [mailto:[email protected]] 
Sent: Thursday, July 21, 2022 4:49 AM
To: denghui (L); [email protected]
Cc: [email protected]; onap-release; [email protected]; 
Catherine LEFEVRE; Kenny Paul; 邓灵莉; yangxu (H)
Subject: Re: Modeling/etsicatalog withdraw form Kohn release
 
[email protected] 
 
Deng,
 
Have you and Yuanhong communicated your status to Keguang?  REQ-1267 is 
dependent on changes to the Modeling project.  Please advise.
 
Keguang - will you need to adjust the scope of REQ-1267?
 
David
 
On Wed, Jul 20, 2022 at 9:32 AM David McBride <[email protected]> 
wrote:
Ok - understood.  Thanks for the update. - D
 
On Tue, Jul 19, 2022 at 6:48 PM denghui (L) <[email protected]> wrote:
Hi David
 
We (Yuanhong Deng together) want to inform you that Modeling/etsicatalog plan 
not join Kohn release, since there is no new feature update needed.
So there is only modeling/modelspec documentation left for K release.
 
Thanks a lot for your checking
Best regards,
 
DENG Hui
 
From: [email protected] [mailto:[email protected]] On Behalf Of 
David McBride
Sent: Wednesday, July 20, 2022 3:59 AM
To: onap-tsc <[email protected]>; onap-release 
<[email protected]>
Cc: Catherine LEFEVRE <[email protected]>; Kenny Paul 
<[email protected]>
Subject: [onap-tsc] Multicloud project withdrawing from the Kohn release #kohn 
#multicloud
 
Team,
 
I was informed, yesterday, that the Multicloud project is withdrawing from the 
Kohn release.
 
David
 
-- 
David McBride (pronounce)
Senior Technical Community Architect
Linux Foundation Networking (LFN)
Mobile: +1.805.276.8018
Email: [email protected]

 
-- 
David McBride (pronounce)
Senior Technical Community Architect
Linux Foundation Networking (LFN)
Mobile: +1.805.276.8018
Email: [email protected]

 
-- 
David McBride (pronounce)
Senior Technical Community Architect
Linux Foundation Networking (LFN)
Mobile: +1.805.276.8018
Email: [email protected]



-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#8786): https://lists.onap.org/g/onap-tsc/message/8786
Mute This Topic: https://lists.onap.org/mt/92522974/21656
Group Owner: [email protected]
Unsubscribe: 
https://lists.onap.org/g/onap-tsc/leave/2743226/21656/1412191262/xyzzy 
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-


Reply via email to