TSC, I took an action during the TSC meeting on June 27 to follow up with the Compass team on the impact of moving the release date for Danube 3 to July 14. Specifically, there was concern about how this might impact work on the Euphrates release.
There are two issues: 1. MS3.2 (integrated SDN scenario deploys and passes health check) occurs on July 11, just 3 days before the proposed July 14 release date for Danube 3. 2. The compass team is operating under a milestone exception for Euphrates. The recovery plan calls for them to be caught up as of MS3.2 on July 11, so their burden for this milestone is greater than it would be, otherwise, without the milestone exception. I had a chance to talk with Justin, the Compass PTL. He indicated that this is not an ideal situation and he will plan to prioritize Euphrates over Danube 3. He said: "Fine with me. But since Danube 3.0 release and Euphrates MS3.2 day are close, so I might have a higher priority in Euphrates" For example, this might result in the new onos-sfc scenario not being released. In my opinion, although the proposed release date presents a challenge for the Compass team, I don't think that it is unreasonable. In addition, if there is a problem, then a remedy may be to reconsider their MS exception plan. Let me know if you have questions or concerns. David -- *David McBride* Release Manager, OPNFV Mobile: +1.805.276.8018 Email/Google Talk: dmcbr...@linuxfoundation.org Skype: davidjmcbride1 IRC: dmcbride
_______________________________________________ opnfv-tech-discuss mailing list opnfv-tech-discuss@lists.opnfv.org https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
