Ghanshyam Mann de457c448b Record deprecated cycle for deprecated project ... Currently project deprecation is done by keeping the project in project.yaml but with release-management as deprecated which is not enough to now is it really deprecated in governance or just release. Also we do not record the deprecation time so that we can remove the project after deprecation is over. Doing it for one project to get agreementon new field and on documenting it on project guide - https://review.opendev.org/#/c/736082/ Follow up will be to add the deprecation cycle for all deprecated repos. Change-Id: I7c801f29b3d2db14e4b215ad965c111be3f359d4		2020-06-17 11:34:32 -05:00
..
tests	s/liasons/liaisons/	2019-07-08 11:42:59 +01:00
__init__.py	move members file parsing into a reusable module	2018-10-08 19:16:34 -04:00
_check_schema.py	add jsonschema validation for project data	2019-07-31 10:03:31 -04:00
_wiki.py	add a script to randomly assign TC members as liaisons	2018-10-09 15:55:24 -04:00
_yamlutils.py	mark yamlutils module as private	2018-11-07 09:05:20 -05:00
governance.py	s/liasons/liaisons/	2019-07-08 11:42:59 +01:00
members.py	Only get git timestamp for generated files	2019-06-26 13:34:25 -05:00
projects.py	Change yaml output to use ruamel.yaml	2019-07-08 16:10:50 +01:00
projects_schema.yaml	Record deprecated cycle for deprecated project	2020-06-17 11:34:32 -05:00
yamltools.py	Change yaml output to use ruamel.yaml	2019-07-08 16:10:50 +01:00