openstack/openstack-manuals
Code Issues Proposed changes
3ef1b62f41
openstack-manuals/doc/contributor-guide/source/release/taskoverview.rst
Doug Hellmann 3ef1b62f41 update end-of-release instructions 
Update the instructions for managing the end of the release to remove
obsolete steps and to include instructions for setting up the new
templates.

Change-Id: Ifc626faa82e403a04ae18297efc8ec280b9db0ee
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
2017-07-21 11:21:48 -04:00

1.4 KiB
Raw Blame History

Release tasks overview

This section provides an overview of the tasks that need to be completed for a documentation release, and a rough schedule of when to complete each task. The schedule is expressed in terms of time before release day. Release day is usually 1300UTC on the initial release date listed on the release schedule.

Four to six weeks before release

Ping packagers to locate pre-release packages to test the Installation Tutorial against, and start looking for willing volunteers to help test.

Four weeks

Ping Cross Project Liaisons (CPLs) to check their chapters, and ping packagers to check on package availability. As soon as pre-release packages are available, ask people to start testing.

Two to four weeks

Ping Speciality Team leads to review and update release notes for openstack-manuals.

At RC1

When projects create their branches and land the first patch, they will automatically have branch-specific documentation. After the branches are created, create the project data file in the openstack-manuals repository for the new series.

Before or on release day

Update the series settings in the template generator and add the landing page for the next series by copying the templates from the current release to the new release directory.