From 521dee84a8d53ebd39dfc0a246f75e239cd11bf2 Mon Sep 17 00:00:00 2001 From: Diego Araújo Date: Sun, 30 Jul 2017 11:44:07 -0300 Subject: [PATCH] [ieeeSW] Review Production Environment Deployment --- ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md b/ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md index f5dcd4c..e2cb26d 100644 --- a/ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md +++ b/ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md @@ -177,10 +177,10 @@ pipeline restarted from scratch. If everything was validated, we moved forward. ### Production Environment Deployment -After the government finished the VE check, it was cleared for deployment and -we could finally began the deployment to Production Environment (PE). For this -we also used our configuration management tool as in the VE as well with same -scripts and package versions. After the deploy was completed, both VE and PE +After the government finished the VE check and it was cleared for deployment, +we could finally begin the deployment to Production Environment (PE). For this +we also used our configuration management tool, the same scripts and package +versions as in the VE. After the deploy was completed, both VE and PE were running identical software. This was the point where new features and bug fixes were finally available to the end users. -- libgit2 0.21.2