Project Name	Preliminary Documentation New docs or new projects ONLY (enter "N/A" if not applicable, or link to gerrit request if completed)	Link to Final Documentation in ReadTheDocs (stable/istanbul branch)	Reviewed by the doc project (reviewed means release related content. Such as release notes and release name were applicable) By best effort!
M2	M4	RC2	Sign Off

Procedure

...

M2

Find JIRA task attached to M1 M2 Epic for your project, if you haven't already done so.
In the table above, fill in the first 4 columns:
- project name
- doc title,
- Project name
- Repositories that contain documentation to be published with the release (one per row)
- Does the repository contain new documentation (yes/no)
- Documentation owner(s) (doc owner (use Confluence @ notation for name, e.g., David McBride)
- current doc state
- activity planned for release
Update status of JIRA task as Done

...

Find JIRA task attached to M2 M4 Epic for your project, if you haven't already done so.
Note that this task applies to new documents only (i.e., "New" in Current Document State column). If this is not a new document, just enter "N/A" in the Preliminary Documentation Completed column in the table above.
For new documents, at a minimum create a placeholder document (e.g., document with a title, or an outline), and commit to the repo. Add a link to the gerrit to the Preliminary Documentation column in the table above.
Update the status of the JIRA task as Done.

Find the dates for the two documentation hackathons.
The document owner should plan on attending at least one of the two hackathons.
Enter a green checkmark in the appropriate column in the table above for the hackathon that was attended.

Find JIRA task attached to RC0 RC2 Epic for your project, if you haven't already done so.
Add a link to the document in ReadTheDocs in the appropriate column in the table above.
Update the status of the JIRA task as Done.

...