blob: 3c3a0c037bc5fe243fb6e3f6568ea1c84e2ac303 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
|
.. This work is licensed under a Creative Commons Attribution 4.0 International License.
.. _updates-and-review:
Updates and Review
==================
Most project owners will need only to concern themselves with their own
project documentation. However, documentation team members and certain
project owners will need to edit and test multiple documentation repositories.
Updates
-------
#. Create a JIRA task in the `ONAP JIRA <https://jira.onap.org/>`_
before you start the updates. The created issue's ID will have to be added to
the commit message.
.. note::
The task should be created in the affected project's workspace. The release
should be specified, as well.
#. If you have not cloned the repository yet, follow the instructions in the
Git guide, section Cloning a repository. If you have done so already, pull the
latest version.
#. Create a local git branch for your changes.
#. Update the required documents in the project repo(s).
#. Build the documentation with tox.
#. Check the output for errors.
#. Add the changed files.
#. Commit your changes. In the commit message, include the issue ID of the
JIRA task, e.g. Issue-ID:DOC-602
#. Request review with git review.
Requesting Reviews
------------------
#. Go to the gerrit review's page included in the output of the git review
command.
#. In gerrit, add the committers for the given
project. For more information, refer to the `Gerrit guide <https://docs.releng.linuxfoundation.org/en/latest/gerrit.html#review>`_.
#. Implement comments by updating your patch, based on
`Updating an existing patch <https://docs.releng.linuxfoundation.org/en/latest/gerrit.html#update-an-existing-patch>`_
in the Gerrit guide.
.. note::
If you already have the branch you need, skip the first 2 steps in the above
guide.
|
