Hi Yuanhong.
Is modeling/etsicatalog still maintained from you/your team?
But for the next release(s) there are no new features expected?
If the answer is “yes”, then it will __not__ be remove from OOM and DOCS – as
far as I know.
But then it needs a “kohn” branch (which can be easily created
Just to clarify …
I think the fact that really matters is: Is „modeling/etsicatalog” planned to
be deployed when ONAP “Kohn” release is installed?
If “yes (deployed with Kohn)”, then you should create a “Kohn” branch, update
the release note (even if it says “nothing new”) and we add it to the
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
hekegu...@chinamobile.com
From: de
Hi Thomas
as previously mentioned, modeling/etsicatalog plans not to join K release, and
we think it’s not necessary to include it in the documentation as well. For
modeling/modelspec, Xu will handle it for the K release.
Thanks for your checking
DENG Hui
From: thomas.ku...@telekom.de [mailto
Hi all.
But please create a ‚Kohn’ branch if you like to see your documentation in the
Kohn release. It is ok that your release note then shows “nothing new in this
release” in this case.
We (doc) will create ‘Kohn’ documentation only from ‘Kohn’ branches!
Thomas
Von: onap-rele...@lists.onap.org
