Download as
Browse Code »

Commit 998f9ac0a5c60cb8c2e190f5ba1041afab72c86c

Authored by Diego Araújo
1 parent ba5c5889
Exists in master and in 3 other branches oss_2018, oss_2018_siqueira, rework_case_study

[ieeeSW] Review Preparing a new release

Showing 1 changed file with 3 additions and 3 deletions   Show diff stats
ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md
  Diff comments   View file @998f9ac
... ... @@ -122,13 +122,13 @@ we moved to preparing the release.
122 122 ### Preparing a new release
123 123  
124 124 Our release process was divided in two perspectives in terms of Git tags: the
125   -application and the SPB Portal. The application tag refers to the specific
126   -feature or bug fix and is a monotonically increasing. A new tag on any system
  125 +application and the SPB Portal. The application tag referred to the specific
  126 +feature or bug fix and was a monotonically increasing. A new tag on any system
127 127 yielded a new SPB Portal tag.
128 128  
129 129 When all tests passed for a given component, we manually created a new
130 130 application tag for it. As a consequence, that automatically created a new tag
131   -for the SPB Portal. Notice that we forked of the original software projects
  131 +for the SPB Portal. Notice that we forked the original software projects
132 132 and, as consequence, we had different tag values.
133 133  
134 134 ### Packaging
... ...