Download as
Browse Code »

Commit c59215cf76884b2dcdd2fff9170e40309d84f759

Authored by Melissa Wen
1 parent 93ea57ac
Exists in master and in 3 other branches oss_2018, oss_2018_siqueira, rework_case_study

[i3eSW] Grammarly last version

Showing 1 changed file with 5 additions and 5 deletions   Show diff stats
ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md
  Diff comments   View file @c59215c
... ... @@ -155,7 +155,7 @@ in partnership with a University is doomed to fail. Our team was not from a
155 155 typical company, consisting mainly of undergraduate students coordinated by two
156 156 professors. At the first year, we had a group composed of 24 undergraduate
157 157 students, one designer, and two senior developers. In 2015, our team grew to 36
158   -students, two designers, eight senior developers. At the end, due to budget
  158 +students, two designers, eight senior developers. In the end, due to budget
159 159 constraint, we had 20 students, one designer, and two developers. On the
160 160 government side, the SPB portal evolution was the first software development
161 161 collaboration between university and government experienced by the MP agents
... ... @@ -193,11 +193,11 @@ project, we became active participants in the deploy operations.
193 193  
194 194 ![Deployment Pipeline](figures/pipeline_3.png)
195 195  
196   -Figure 1 represents our CD pipeline. A new feature might require changes on
  196 +Figure 1 represents our CD pipeline. A new feature might require changes to
197 197 more than one SPB integrated software project. Notice that each one of them
198 198 could be modified independently. The pipeline started when new code arrived. As
199 199 it went through each step, it was tested and improved until it finally reached
200   -the production environment. At this point we would restart the pipeline to
  200 +the production environment. At this point, we would restart the pipeline to
201 201 release more new code.
202 202  
203 203 ### Automated Tests
... ... @@ -242,7 +242,7 @@ repository.
242 242 We decided to create own packages for each software component for the following
243 243 five reasons:
244 244  
245   -1. Not all software was packaged by the community and those that existed were outdated;
  245 +1. The community packaged not all software, and those that existed were outdated;
246 246 1. Packaging makes it easy to manage the software on a given distribution;
247 247 1. Packaging simplifies the deployment;
248 248 1. Packaging follows the distribution's best practices and,
... ... @@ -280,7 +280,7 @@ we moved forward.
280 280 ### Production Environment Deployment
281 281  
282 282 When the MP agents finished the VE check, we could finally begin the deployment
283   -in the PE. For this we also used our configuration management tool, the same
  283 +in the PE. For this, we also used our configuration management tool, the same
284 284 scripts and package versions as in the VE. After the deploy was completed, both
285 285 VE and PE were running identical software. Here was the point where new
286 286 features and bug fixes were finally available to the end users.
... ...