Hi Ray,
While I see that Ocata is a shorter release cycle the Pike release is within a couple of weeks of the same date as Newton. My guess would be that if we delay Danube to skip newton we would have 2 OPNFV releases with an Ocata based VIM. Danube set’s challenges across a variety of project delivery dates where we may not be able to “squeeze in the difference” to accommodate for coordination. I’m not sure that there is a lot of benefit in OPNFV making significant changes to our cadence based on that. Maybe once we have our CI evolution process in place we can establish some form of predictable metric (and improvements) around the time it takes to stabilize once our upstream communities release. (not all upstream are equal in that aspect.) Maybe the right answer is to try and pull back our own cycles based on improvements in our own integration activities. It could also be that we use our “cadence” as a guideline and look to release in a +/- one month window based on multi-project cross community planning. / Chris From: <[email protected]> on behalf of Raymond Paik <[email protected]> Date: Thursday, 3 November 2016 at 06:38 To: TECH-DISCUSS OPNFV <[email protected]> Subject: [opnfv-tech-discuss] Which OpenStack release for Danube? Another follow-up from the TSC call. OpenStack-Ocata is scheduled to release in late February (see http://www.openstack.org/ptg#tab_about) and a question was raised during OpenStack Summit last week if we should consider delaying the Danube release so that Ocata (vs. Newton) will be part of Danube. Some people were supportive of including the latest release of OpenStack, but there were also concerns about "skipping" the Newton release. Let's continue the conversation on this thread... Thanks, Ray _______________________________________________ opnfv-tech-discuss mailing list [email protected] https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
_______________________________________________ opnfv-tech-discuss mailing list [email protected] https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
