From d401614c51079f436182e15e330141a6326d3ee7 Mon Sep 17 00:00:00 2001 From: Rafael Reggiani Manzo Date: Thu, 27 Jul 2017 20:43:22 -0300 Subject: [PATCH] [ieeeSW] Review production deployment description --- ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md b/ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md index d112e51..f0732d4 100644 --- a/ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md +++ b/ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md @@ -194,11 +194,12 @@ move forward. ### Production Deployment -After the government authorizes the VE, we can finally begin the production -deployment. We use the same configuration management tool with the same -scripts. After the deploy is completed, both VE and PE are on the same state. -The new features and bug fixes are finally available to end users. - +After the government finish the VE check, it is cleared for deployment and we +can finally begin the deployment to Production Environment (PE). For this we +use the same configuration management tool as in the VE as well with same +scripts and package versions. After the deploy is completed, both VE and PE +are running identical software. This is the point where new features and bug +fixes are finally available to end users. ## Benefits -- libgit2 0.21.2