Team,
I've gotten some questions about continuing a requirement from one release
to the next. So, for example, from Guilin to Honolulu.
In order to track history, we decided that it would be better to create a
new issue, rather than change the "fixversion" field on the original
field. That way, the history of the scorecards, tsc approvals, scope, etc.
does not get reset.
Process:
Current Issue:
1. Add a comment:
- What was completed
- What remains to be done
- Assert that the requirement will be continued in the next release
2. Change the "scope status" to "reduced scope"
3. Update the Jira status as "Done"
New Issue
1. Create a new issue with identical summary as the previous issue.
2. Set fixversion to the target release version (e.g., Honolulu Release).
3. In the "Issue Links" field, add a link to the previous issue.
4. Add a comment indicating that this issue is a continuation of a
previous issue (add Jira reference)
Please let me know if you have any questions.
David
--
*David McBride*
Release Manager
Linux Foundation Networking (LFN)
Mobile: +1.805.276.8018
Email: dmcbr...@linuxfoundation.org
IRC: dmcbride
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#7336): https://lists.onap.org/g/onap-tsc/message/7336
Mute This Topic: https://lists.onap.org/mt/78664514/21656
Mute #guilin:https://lists.onap.org/g/onap-tsc/mutehashtag/guilin
Mute #honolulu:https://lists.onap.org/g/onap-tsc/mutehashtag/honolulu
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
