Hi, I would like to share some feedback from my Nokia colleagues about “collateral damage” done by this merge. *For several weeks prior to the merge it was not possible to get code merge requests in SO approved due to the imminent code change. * As part of this merge, some tests created by the Nokia contributors were incompatible with the new code and failed. As a workaround they were ignored. The AT&T developers are already supporting the fix of these tests, but it would have been best to handle this earlier.
Needless to say that in addition to the actual issues, this is counter-productive in the effort to drive more contribution from Nokia, as well as other community members. Our request is to have some more transparency and collaboration in the process leading to such large merges, or better yet, avoid them altogether if possible. Regards, Ranny. From: [email protected] <[email protected]> On Behalf Of Kenny Paul Sent: Tuesday, July 31, 2018 12:52 PM To: onap-tsc <[email protected]> Subject: [onap-tsc] FYI on Ecomp 1806 code merge This is just an FYI for transparency due to the unusual size of the merge, to align the AT&T codebase with SO. Previously identified as a risk in the M2 review as approved by the TSC, this merge was completed today. As a result of this merge there will be better resource alignment for SO development moving forward. https://gerrit.onap.org/r/#/c/58247/ +460794, -406085 Best Regards, -kenny Kenny Paul, Technical Program Manager, The Linux Foundation [email protected]<mailto:[email protected]>, 510.766.5945 San Francisco Bay Area, Pacific Time Zone -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#3565): https://lists.onap.org/g/ONAP-TSC/message/3565 Mute This Topic: https://lists.onap.org/mt/23938219/21656 Group Owner: [email protected] Unsubscribe: https://lists.onap.org/g/ONAP-TSC/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
