From df4ddacf201bac6d11ecbcda59f8ae7d9ebf4b06 Mon Sep 17 00:00:00 2001 From: Ori Hoch Date: Tue, 23 Feb 2016 15:15:54 +0200 Subject: [PATCH] project management docs: add details about deployment --- docs/devel/source/project_management.rst | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/docs/devel/source/project_management.rst b/docs/devel/source/project_management.rst index c5a1c327..583a1b0e 100644 --- a/docs/devel/source/project_management.rst +++ b/docs/devel/source/project_management.rst @@ -2,9 +2,6 @@ Project Management ================== -Reviewing and Merging Pull Requests -=================================== - Pull Request Code Review ------------------------ @@ -36,3 +33,8 @@ Look at a few previous releases to see what's written in the release notes, and Generally, release notes are meant for non technical people as well, so you should write a few words about the changes that were introduced. Also, you can write deployment notes if any special actions should be performed before or after the deployment. + +Deploying a release +------------------- + +Once you have some pull requests merged you might want to deploy the release. The release should be published before deployment (click "Publish" button in GitHub edit release page). This allows us to know which version was deployed. For technical details about how to deploy see the DevOps documentation.