Sorry for the late email. My vote is -1
Personally I suggest to drop Danube release 3 and let's focus on the release of Euphrates 1.0. Currently most of the installers are busy on integrating and it is still a challenge for them. I would like to give the installers more time and resources in the next release. Julien Raymond Paik <[email protected]>于2017年7月13日周四 下午9:29写道： > Thank to everyone who sent your votes. > > There were eleven +1 votes and one -1 vote, thus the release date of July > 14th has been approved. > (Trevor, Ross, and Viktor sent their +1 votes just to me via email. They > are proxies for Brian Skerry, Jack, and Tapio respectively.) > > Ray > > On Thu, Jul 13, 2017 at 12:02 AM, Juraj Linkes -X (jlinkes - PANTHEON > TECHNOLOGIES at Cisco) <[email protected]> wrote: > >> +1 >> >> >> >> *From:* [email protected] [mailto: >> [email protected]] *On Behalf Of *Raymond Paik >> *Sent:* Tuesday, 11 July, 2017 17:50 >> *To:* [email protected] >> *Cc:* [email protected] >> *Subject:* [opnfv-tech-discuss] TSC vote requested for Danube 3.0 release >> >> >> >> All, >> >> >> >> After checking with several scenarios owners during the Release call >> today, there was a consensus that people were ready to tag for the Danube >> 3.0 release on July 14th. There were some scenarios with degradation >> compared to 1.0 or 2.0 releases, but they would be explained in >> documentations (e.g. due to upstream bug). >> >> >> >> So, I'd like to ask the TSC members to vote on the following by 5pm >> Pacific Time July 12th. >> >> >> >> "Does the TSC approve the Danube 3.0 release date of July 14? (+1, 0, >> -1)" >> >> >> >> Thanks, >> >> >> >> Ray >> > > _______________________________________________ > opnfv-tsc mailing list > [email protected] > https://lists.opnfv.org/mailman/listinfo/opnfv-tsc >
_______________________________________________ opnfv-tech-discuss mailing list [email protected] https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
