Commit 8595b27f08cdb786734e4929c78cbe15244c0bfa
1 parent
d401614c
Exists in
master
and in
3 other branches
[ieeeSW] Fix figure
The first stage does not regards requirement gathering but actually code ready for deployment that comes from each development team. This required the caption to change as well.
Showing
3 changed files
with
4 additions
and
10 deletions
Show diff stats
ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md
| ... | ... | @@ -96,18 +96,12 @@ the worst political crisis after the re-democratization in Brazil. |
| 96 | 96 | |
| 97 | 97 | ## Our Continuous Delivery Pipeline |
| 98 | 98 | |
| 99 | -[//]: # (TODO - Fazer a imagem. Sem esquentar muito a cabeça, uma vez que a revista deve refazer tal imagem) | |
| 100 | - | |
| 101 | -[//]: # (conjunto de features -> testes automatizados → criação de tag → empacotamento →deploy em homologação → testes de aceitação → deploy em produção) | |
| 102 | - | |
| 103 | -[//]: # (TODO - Rever essa frase - é uma legenda da imagem?) | |
| 104 | - | |
| 105 | 99 |  |
| 106 | 100 | |
| 107 | -The figure represents our CD pipeline: each release starts with specific | |
| 108 | -requirements which are refined and improved during development as they go | |
| 109 | -through each one of the steps until finally reach the production environment. | |
| 110 | -At this point a new set of requirements is built and a new release starts. | |
| 101 | +The figure represents our CD pipeline: it starts with new code arriving | |
| 102 | +which is tested and improved during as necessary as it goes through each one | |
| 103 | +of the steps until finally reaches the production environment. At this point | |
| 104 | +we get back to the first stage to release more new code. | |
| 111 | 105 | |
| 112 | 106 | ### Automated tests |
| 113 | 107 | ... | ... |
ieeeSW/releaseEng3/figures/pipeline.dia
No preview for this file type
ieeeSW/releaseEng3/figures/pipeline.png
