launchpad-reviewers team mailing list archive
-
launchpad-reviewers team
-
Mailing list archive
-
Message #28475
[Merge] ~jugmac00/launchpad-buildd:update-deployment-documentation into launchpad-buildd:master
Jürgen Gmach has proposed merging ~jugmac00/launchpad-buildd:update-deployment-documentation into launchpad-buildd:master.
Commit message:
Update deployment instructions
Requested reviews:
Launchpad code reviewers (launchpad-reviewers)
For more details, see:
https://code.launchpad.net/~jugmac00/launchpad-buildd/+git/launchpad-buildd/+merge/422985
--
Your team Launchpad code reviewers is requested to review the proposed merge of ~jugmac00/launchpad-buildd:update-deployment-documentation into launchpad-buildd:master.
diff --git a/docs/how-to/deployment.rst b/docs/how-to/deployment.rst
index a52be76..c44d543 100644
--- a/docs/how-to/deployment.rst
+++ b/docs/how-to/deployment.rst
@@ -6,15 +6,18 @@ The following steps need to be performed before `Upgrading the builders
1. Ensure everything has been merged to master.
-2. Create a new release branch, based on master.
+2. Create a new release branch, e.g. ``release-213``, based on master.
-3. Run ``DEBEMAIL="<email address>" DEBFULLNAME="<name>" dch -rD bionic``.
+3. Run ``DEBEMAIL="<email address>" DEBFULLNAME="<name>" dch -rD focal``.
The later recipe build will prepend the correct preamble for each Ubuntu release.
-4. Commit and push this branch, open a MergeProposal for review.
+4. Create a commit with a title like ``releasing package launchpad-buildd version 213``,
+ push this branch and open a MergeProposal with a title like
+ ``Release version 213``for review.
5. Once the release branch has merged to master,
- tag the release commit and check https://code.launchpad.net/~launchpad/+recipe/launchpad-buildd-daily
+ tag the release commit (e.g. ``git tag 213 && git push origin --tags``) and
+ check https://code.launchpad.net/~launchpad/+recipe/launchpad-buildd-daily
for the recipe build to happen.
You can start a build if required.