Commit 9cb373898a4cf5697b2459c0a49d2ad7f60bcfa7
1 parent
4cf01cd1
Exists in
master
and in
3 other branches
[i3eSW] Minor fixes
Showing
1 changed file
with
2 additions
and
2 deletions
Show diff stats
ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md
... | ... | @@ -286,13 +286,13 @@ available to allocate for the building of the pipeline. The construction and |
286 | 286 | maintenance of the CD process were possible by taking some decisions to mature |
287 | 287 | the project: |
288 | 288 | |
289 | -1. _Selecting the most experienced professionals and some developers of the | |
289 | +1. _Select the most experienced professionals and some developers of the | |
290 | 290 | project to work on a specific team for DevOps._ These professionals used their |
291 | 291 | experiences in OSS projects to get an initial proposal for the deployment process. |
292 | 292 | The solution enabled us to automate the deployment, even though the process was |
293 | 293 | still rudimentary. |
294 | 294 | |
295 | -2. _Interchanging team members and encouraging teammates to migrate to DevOps | |
295 | +2. _Interchange team members and encouraging teammates to migrate to DevOps | |
296 | 296 | team._ The benefits of these movements were twofold: mitigating the difficulty |
297 | 297 | to pass the knowledge between DevOps developers and features developers, and |
298 | 298 | evolving the process on-the-fly. | ... | ... |