+1... Committers: please verify that bugs committed to stable/1807 have Jira tickets, address critical issues, and won’t cause collateral damage. The 18.07 release is only 1 week away!
Thanks... Dave From: vpp-dev@lists.fd.io <vpp-dev@lists.fd.io> On Behalf Of Edward Warnicke Sent: Monday, July 23, 2018 3:50 PM To: vpp-dev <vpp-dev@lists.fd.io> Subject: [vpp-dev] VPP 18.07 Release Milestone RC2 is complete! Folks, I have created the v18.07-rc2 tag on stable/1807 I will be verifying that 18.07-rc2 build artifacts have been uploaded to nexus.fd.io<http://nexus.fd.io>. VPP 18.07 Release Milestone RC2 is complete! As a reminder, the VPP 18.07 Release next Monday Jul 30, 2018. https://wiki.fd.io/view/Projects/vpp/Release_Plans/Release_Plan_18.07#Release_Milestones<https://wiki.fd.io/view/Projects/vpp/Release_Plans/Release_Plan_18.01#Release_Milestones> It is important that only bugs which address critical issues (as determined by the VPP committers), ideally limited to addressing bugs found by CSIT testing. Per the standard process, all bug fixes to stable branches should follow the best practices: * All bug fixes must be double-committed to the release throttle as well as to the master branch * Commit first to the release throttle, then "git cherry-pick" into master * Manual merges may be required, depending on the degree of divergence between throttle and master * All bug fixes need to have a Jira ticket * Please put Jira IDs into the commit messages. * Please use the same Jira ID for both the stable branch and master. Ed
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#9913): https://lists.fd.io/g/vpp-dev/message/9913 Mute This Topic: https://lists.fd.io/mt/23796480/21656 Group Owner: vpp-dev+ow...@lists.fd.io Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
