Gildas, A jira item could span multiple repositories in a project - for instance documentation affected multiple repos. Developers will use judegment when referencing the jira item for a project. We dont need to add more overhead.
Brian From: onap-discuss-boun...@lists.onap.org [mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Gildas Lanilis Sent: Tuesday, October 03, 2017 7:17 PM To: onap-discuss@lists.onap.org Subject: [onap-discuss] Practices on the usage of Jira-ID in the commit Dear Community Members, It came to my knowledge that some Jira IDs are, in some case, not been used properly when committing code. To overcome this issue, please consider these cases: 1. If you commit some code in project A, ensure the Jira ID is reflecting the same project A. 2. Each issue is unique, and do not re-use the same Jira ID within the same project (unless it is a bug this is difficult to fix and requires multiple commits). As we are entering in the integration phase, it is becoming more and more critical that we have a clear view on what goes into the release, I kindly request you abide to these practices. Thanks, Gildas [HuaweiLogowithName] Gildas Lanilis ONAP Release Manager Santa Clara CA, USA gildas.lani...@huawei.com<mailto:gildas.lani...@huawei.com> Mobile: 1 415 238 6287
_______________________________________________ onap-discuss mailing list onap-discuss@lists.onap.org https://lists.onap.org/mailman/listinfo/onap-discuss
