From 6e2e8e69d5d0b9f7ecd97d3d90243bfee736f63f Mon Sep 17 00:00:00 2001 From: Diego Araújo Date: Tue, 14 Nov 2017 14:02:12 -0200 Subject: [PATCH] [ieeeSW] Grammarly on Shared Responsibility section --- ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md b/ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md index 6b9772a..0d36bc2 100644 --- a/ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md +++ b/ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md @@ -248,13 +248,13 @@ would not go looking for other jobs. ### Shared Responsibility Initially, the development team could not track what happened to the code after -its delivery, since government technicians were the only responsible for +its delivery, since government technicians were the only ones responsible for deploying the project. The implementation of CD made developers feel equally responsible for what was getting into production and take ownership of the project. % Interestingly, the CD pipeline had the same effect on the team of requirement -analysts. They became more engaged on the whole process, opening and discussing +analysts. They became more engaged in the whole process, opening and discussing issues during the platform evolution. Additionally, developers worked to improve the CD pipeline to speed up the process of making new features available in the production environment for analysts’ validation. -- libgit2 0.21.2