P02: Create documentation for an ONAP release (ONAP project teams)

TITLE	P02: Create documentation for an ONAP release (ONAP project teams)
SUBJECT	Procedure #02 describes the required tasks which must be performed by ONAP project teams to create their release-specific documentation for an ONAP main and maintenance release.
TARGET AUDIENCE	ONAP project teams: Maintainers of project repository
RELEASE RELEVANCE	R12 'London' - R11 'Kohn'
TABLE OF CONTENTS	1 MASTER BRANCH PREPARATION 1.1 Create a new Jira task and use the ID for all upcoming changes 1.2 Clone 'master' branch of your repository to your local development environment 2 MASTER BRANCH UPDATES 2.1 Ensure correct 'defaultbranch' in '.gitreview' 2.2 Update Sphinx configuration file 'conf.py' 2.3 Update Sphinx configuration file 'requirements-docs.txt' 2.4 Update Tox configuration file 'tox.ini' 2.5 Update ReadTheDocs build configuration file '.readthedocs.yaml' 2.6 Update ReadTheDocs configuration file 'ribbon.css' 2.7 Update your project release notes 2.8 Update your documentation files 3 RELEASE BRANCH PREPARATION 3.1 Create new branch of your repository using gerrit 3.2 Clone '{release}' branch of your repository to your local development environment 4 RELEASE BRANCH UPDATES 4.1 Set correct 'defaultbranch' in '.gitreview' 4.2 Update Sphinx build configuration file 'conf.py' 4.3 Update Tox configuration file 'tox.ini' 4.4 Update at least one .rst file to trigger the RTD build 5 IMPROVEMENTS FOR THIS PROCEDURE 5.1 To be discussed 5.2 To be done
AUTHOR	@Thomas Kulik
REVIEWER	@Toine Sie

P02: Create documentation for an ONAP release (ONAP project teams)

TITLE

P02: Create documentation for an ONAP release (ONAP project teams)

SUBJECT

TARGET AUDIENCE

RELEASE RELEVANCE

TABLE OF CONTENTS

AUTHOR

REVIEWER