Download as
Browse Code »

Commit d16b4fd1b8032bf9d238bff81233d3be64991194

Authored by Rafael Reggiani Manzo
1 parent fe6b39d5
Exists in master and in 3 other branches oss_2018, oss_2018_siqueira, rework_case_study

[ieeeSW] Review release process

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