From 9f88d58f33ee13d29afd18e8c3a843582099d070 Mon Sep 17 00:00:00 2001 From: Doug Hellmann Date: Tue, 6 Nov 2018 11:35:01 -0500 Subject: [PATCH] document policy on adding new deliverables Change-Id: I639eecf05e0dcd6bee5e4390c80ce491a8fefc39 Story: 2001845 Task: 12613 Signed-off-by: Doug Hellmann --- doc/source/reference/release_models.rst | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/doc/source/reference/release_models.rst b/doc/source/reference/release_models.rst index e0d2692148..e0b54c1670 100644 --- a/doc/source/reference/release_models.rst +++ b/doc/source/reference/release_models.rst @@ -169,3 +169,15 @@ a library were to need large feature development work again, we'd have two options: develop the new feature in a new library depending on the stable one, or grant an exception and switch it back to the `cycle-with-intermediary`_ model. + +Adding Deliverables +=================== + +In order to be considered to be included in the release for a given +series, the project must be documented by adding a deliverable file to +this repository before the second milestone of the series. + +Projects created or added to governance after the second milestone +should be released using the independent release model, and then +changed to one of the cycle-based models at the start of the next +cycle.