...
- Decide with team if a bug should be dropped back to previous release or not, consider things like (use fix-version field in Jira to indicate this)
- bug was reported by user of previous release (easy decisionÂ
)
- bug exposes behavior that was not in line with acceptance criteria for a user story that was delivered in previous release
- bug was reported by user of previous release (easy decisionÂ
- Make the fix and have it merged in master branch
- use minimal code to avoid merge/drop back issues
- specific test for bug fix should be included where possible
- Cherry pick the fix from master branch to release branch
- From Gerrit:
- Navigate to ... / Cherry Pick
- Fill the form with the release branch name (honolulu) in "Cherry Pick to branch" field and click "Cherry Pick"
- Using local branch (to resolve cherry-pick conflicts):
- Create local branch from honolulu
- Cherry-pick commit from master branch
- Resolve conflicts
- git push origin HEAD:refs/for/honolulu (or git review)
- From Gerrit:
- Review patch by peers as normal
- To facilitate the review, ensure that gerrit merge requests both in master and release branches have the same topic Topic value including Jira Issue ID , then related fixes can be easily retrieved (ex: https://gerrit.onap.org/r/q/topic:%2522bugfix/CPS-292-error-details%2522intopic:+%2522CPS-292%2522). Then, related fixes can be easily filtered or clicking on the Topic field from one change provides the list of all related ones).
- To facilitate the review, ensure that gerrit merge requests both in master and release branches have the same topic Topic value including Jira Issue ID , then related fixes can be easily retrieved (ex: https://gerrit.onap.org/r/q/topic:%2522bugfix/CPS-292-error-details%2522intopic:+%2522CPS-292%2522). Then, related fixes can be easily filtered or clicking on the Topic field from one change provides the list of all related ones).
- Update Release version in a separate commit if and when required
A few bugs can be combined in one patch.
Release notes doc should be updated too
Typically only the 'patch' number (last digit) should be increased. See also - Once the fix is in release branch, deliver releases artifacts from release branch as described in previous section.
...