Dear all, Let me provide the status update for our blocking issue in the master branch.
It seems that we managed to bring master to a workable state. Currently we have a workaround for the nasty bug in VID but I'm working on proper solution that we hope to merge before EOW. This means that we finally unlocked our OOM review pipeline. We believe that the realistic date for RC0 is next Thursday (25th). As the number of reviews (>70) in our pipeline is overwhelming for the work force that we've performed a triage on those patches has been performed. We divided all patches into 3 categories: Bugfixes (from the OOM perspective): https://gerrit.onap.org/r/q/hashtag:%22bugfix%22+(status:open%20OR%20status:merged) Reviews created before M3: https://gerrit.onap.org/r/q/hashtag:%22beforem3%22+(status:open%20OR%20status:merged) Reviews created after M3: https://gerrit.onap.org/r/q/hashtag:%22afterm3%22+(status:open%20OR%20status:merged) OOM patches are going to be processed in this order. We'll do our best to review and merge category 1 & 2 before RC0 but to make it happen we really need project teams to be supportive and fix issues reported in the review promptly. * IMPORTANT NOTE TO PTLs: * We are using gerrit hashtags for our triage process thus please DO NOT MODIFY TAGS ASSIGNED BY THE OOM TEAM ON YOUR OWN. You can always write an email or catch us on slack and discuss if sth from 3rd category has to be merged for Honolulu but don't move your patch between categories on your own. Best regards, -- Krzysztof Opasiak Samsung R&D Institute Poland Samsung Electronics -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#7634): https://lists.onap.org/g/onap-tsc/message/7634 Mute This Topic: https://lists.onap.org/mt/81413900/21656 Group Owner: onap-tsc+ow...@lists.onap.org Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/21656/1412191262/xyzzy [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
