From 998f9ac0a5c60cb8c2e190f5ba1041afab72c86c Mon Sep 17 00:00:00 2001 From: Diego Araújo Date: Sun, 30 Jul 2017 11:23:21 -0300 Subject: [PATCH] [ieeeSW] Review Preparing a new release --- ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md b/ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md index 0397895..a0ae466 100644 --- a/ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md +++ b/ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md @@ -122,13 +122,13 @@ we moved to preparing the release. ### Preparing a new release Our release process was divided in two perspectives in terms of Git tags: the -application and the SPB Portal. The application tag refers to the specific -feature or bug fix and is a monotonically increasing. A new tag on any system +application and the SPB Portal. The application tag referred to the specific +feature or bug fix and was a monotonically increasing. A new tag on any system yielded a new SPB Portal tag. When all tests passed for a given component, we manually created a new application tag for it. As a consequence, that automatically created a new tag -for the SPB Portal. Notice that we forked of the original software projects +for the SPB Portal. Notice that we forked the original software projects and, as consequence, we had different tag values. ### Packaging -- libgit2 0.21.2