Commit bab08ca33dd62e31d32e21eccc68fd77ff3695ba
1 parent
0e98abf2
Exists in
master
and in
3 other branches
Final version!
Showing
1 changed file
with
2 additions
and
2 deletions
Show diff stats
ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md
... | ... | @@ -277,7 +277,7 @@ available to build the initial version of the pipeline. The construction and |
277 | 277 | maintenance of the CD process were made possible by the key decisions to: |
278 | 278 | |
279 | 279 | 1. _Select the most experienced senior developers and some advanced interns to |
280 | -work on a specific DevOps team._These senior developers used their experience | |
280 | +work on a specific DevOps team._ These senior developers used their experience | |
281 | 281 | in OSS projects to craft an initial proposal for the deployment process. The |
282 | 282 | solution enabled us to automate the deployment, even though the process was, |
283 | 283 | initially, still rudimentary. |
... | ... | @@ -321,7 +321,7 @@ both VE and PE. |
321 | 321 | |
322 | 322 | In summary, we encourage the use of a well-thought CD pipeline as a means to |
323 | 323 | gain trust in software development projects with government and large |
324 | -organizations. | |
324 | +organizations as well. | |
325 | 325 | |
326 | 326 | ## References |
327 | 327 | ... | ... |