Download as
Browse Code »

Commit fe6b39d5cfe8a1509994c4196106c2a2f9c64e54

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

Replace 'PSPB' by 'SPB Portal' 

This makes the pipeline description consistent with the context
description term first use.
Showing 1 changed file with 5 additions and 5 deletions   Show diff stats
ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md
  Diff comments   View file @fe6b39d
@@ -135,15 +135,15 @@ Only after all tests passed we move to the next step down the pipeline. @@ -135,15 +135,15 @@ Only after all tests passed we move to the next step down the pipeline.
135 ### Preparing a new release 135 ### Preparing a new release
136 136
137 Our release system was divided into two perspectives: the application and the 137 Our release system was divided into two perspectives: the application and the
138 -PSPB. 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 PSPB tag. 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.
140 140
141 When all tests passed for a given component, we manually created a new 141 When all tests passed for a given component, we manually created a new
142 application tag for it. As a consequence, that automatically created a new tag 142 application tag for it. As a consequence, that automatically created a new tag
143 -for the PSPB. Notice that we have forks of the original softwares and, as 143 +for the SPB Portal. Notice that we have forks of the original softwares and, as
144 consequence, we had different tag values. Packaging 144 consequence, we had different tag values. Packaging
145 145
146 -The PSPB platform is running under the CentOS GNU/Linux distribution. 146 +The SPB Portal platform is running under the CentOS GNU/Linux distribution.
147 Basically, packaging a software for that distribution has three steps: (1) 147 Basically, packaging a software for that distribution has three steps: (1)
148 write the script for the specific environment (RPM), (2) build the package, and 148 write the script for the specific environment (RPM), (2) build the package, and
149 (3) upload it to a package repository. We chose to package our components for 149 (3) upload it to a package repository. We chose to package our components for
@@ -181,7 +181,7 @@ The VE was used by the government agents to validate new features and required @@ -181,7 +181,7 @@ The VE was used by the government agents to validate new features and required
181 changes. Also, the VE was useful to verify the integrity of the entire portal 181 changes. Also, the VE was useful to verify the integrity of the entire portal
182 as part of the next step in the pipeline. Acceptance Tests 182 as part of the next step in the pipeline. Acceptance Tests
183 183
184 -After we completely deploy a new PSPB version in the VE, the government agents 184 +After we completely deploy a new SPB Portal version in the VE, the government agents
185 are responsible for checking features and/or bug fixes required by them. If the 185 are responsible for checking features and/or bug fixes required by them. If the
186 technicians identify a problem, they notify the developers, the problems are 186 technicians identify a problem, they notify the developers, the problems are
187 fixed and the pipeline restarts from scratch. If everything is validated, we 187 fixed and the pipeline restarts from scratch. If everything is validated, we