Re: [onap-discuss] SECCOM 5 April update for PTLs
Are the repos for these projects marked as readonly in Gerrit?
Is there a release name or date available for each of these as to when they were first considered unmaintained? An example might be “beginning with the Honolulu release.”
It would also be good if the wiki pages that https://wiki.onap.org/display/DW/Unmaintained+State+Projects points to were to be modified to indicate clearly that they are indeed unmaintained.
Examples from the CII badging folks on how to clearly mark a project as unmaintained that apply to ONAP are:
For example, use “DEPRECATED” as the first heading of its README title, . . . add a no-maintenance-intended badge ( https://unmaintained.tech/ ) in its README, and/or use the code repository's marking system (e.g., . . . Gerrit's "readonly" status, . . .). Additional discussion can be found here: https://medium.com/maintainer-io/how-to-deprecate-a-repository-on-github-8f0ceb9155e .
From: <onap-discuss@...> on behalf of Thomas Kulik <thomas.kulik@...>
A general definition can be found here:
Project State: Unmaintained
The list of unmaintained state projects is here:
Von: fabian.rouzaut@... <fabian.rouzaut@...>
Do we have a list for the ‘unmaintained project”?
Just a small hint about wording: Please use „unmaintained“ instead of “in maintenance mode”.
last weekly report available here (it includes the RC0): https://logs.onap.org/onap-integration/weekly/onap_weekly_pod4_master/2021-04/03_22-48/security/versions/versions.html
Java 8: 24+3 (dual java8 and java11)
Python 2.7: 13 + 10 (dual python 2.7 and python 3)
if we look at the issues
- portal: in maintenance mode since Honolulu
- music: in maintenance since Guilin
- msb: not sure that it is officially in maintenance but not lots of changes recently
- esr: in maintenanc emode since Guilin
- appc in maintenance mode since Guilin
- appc: in maintenance mode since Guilin
- awx: tooling
- robot: tooling
I raised the question on appc in a gerrit as the HC is also regularly FAIL
As far as I can see appc is still mentioned in 2 use cases (vFWDT and scaleout) but should we not
- remove appc from the deployment
- in the vFWDT and scaleout use case doc, if they are still maintained, indicate how to launch the old appc for the use case but not include appc in teh official honolulu deployment
I know that there was a working group on this topic and that the question of dependencies is tricky..music > OOF,, MSB > CNF use cases...
onap-discuss@... [onap-discuss@...] de la part de Amy Zwarico [amy.zwarico@...]
5 April SECCOM update for the PTLs.
Amy Zwarico, LMTS
Chief Security Office / Platform Security