Project

Profile

Help

Task #3131

closed

Create docs on a release preparation process

Added by bmbouter over 6 years ago. Updated almost 5 years ago.

Status:
CLOSED - COMPLETE
Priority:
High
Assignee:
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Platform Release:
Groomed:
No
Sprint Candidate:
Yes
Tags:
Documentation, Pulp 2
Sprint:
Quarter:

Description

With a focus on Pulp3, Pulp2 (I think) is switching to be a feature-driven release. We don't have a documented, open way to organize when a release will occur and what is going into it. For now this will be scoped to Pulp2 since Pulp3 is still in alpha.

We will still use the same "release train" process which includes a release page on the wiki to track the release (like this one), but this will cause the "release train" to start in a request-driven way via an open process.

Let's post some ideas on this ticket, which can be aggregated into either a wiki doc or the pulp docs. Here are some starter questions:

What info is needed from developers to request the "release train" be started?
How much time notice is needed for release engineering to create a beta after it is requested?
What is the role of QE in requesting a "release train" to be started?
How will the request be sent, and how will it be acknowledged?
Where will this process be documented? Maybe In the Pulp2 docs or in a wiki page?

Also available in: Atom PDF