Commit 852a846e0f8f0b6e53863d74b0cabefaa6102767
Exists in
master
and in
3 other branches
Merge branch 'master' of softwarepublico.gov.br:softwarepublico/articles
Showing
1 changed file
with
7 additions
and
4 deletions
Show diff stats
ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md
@@ -131,14 +131,17 @@ Only after all tests passed we move to the next step down the pipeline. | @@ -131,14 +131,17 @@ Only after all tests passed we move to the next step down the pipeline. | ||
131 | 131 | ||
132 | ### Preparing a new release | 132 | ### Preparing a new release |
133 | 133 | ||
134 | -Our release system was divided into two perspectives: the application and the | ||
135 | -SPB Portal. The application tag refers to the specific feature or bug fix and is a | ||
136 | -monotonically increasing. A new tag on any system yielded a new SPB Portal tag. | 134 | +Our release process was divided in two perspectives in terms of git tags: the |
135 | +application and the SPB Portal. The application tag refers to the specific | ||
136 | +feature or bug fix and is a monotonically increasing. A new tag on any system | ||
137 | +yielded a new SPB Portal tag. | ||
137 | 138 | ||
138 | When all tests passed for a given component, we manually created a new | 139 | When all tests passed for a given component, we manually created a new |
139 | application tag for it. As a consequence, that automatically created a new tag | 140 | application tag for it. As a consequence, that automatically created a new tag |
140 | for the SPB Portal. Notice that we have forks of the original softwares and, as | 141 | for the SPB Portal. Notice that we have forks of the original softwares and, as |
141 | -consequence, we had different tag values. Packaging | 142 | +consequence, we had different tag values. |
143 | + | ||
144 | +### Packaging | ||
142 | 145 | ||
143 | The SPB Portal platform is running under the CentOS GNU/Linux distribution. | 146 | The SPB Portal platform is running under the CentOS GNU/Linux distribution. |
144 | Basically, packaging a software for that distribution has three steps: (1) | 147 | Basically, packaging a software for that distribution has three steps: (1) |