2016-11-17 03:51, Xu, Qian Q: > It is good that RC1 on Jan.11th is a hard deadline. We also need ensure that > RC1 is a complete package with all features. If RC1 is out but missing some > big features, then the test results on RC1 vs RC2 may have big difference. > So, could we ensure that RC1 is a complete feature package, if any feature > missing RC1, then we may postpone the feature to 17.05? Does it make sense?
Absolutely, yes. > -----Original Message----- > From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Thomas Monjalon > Sent: Tuesday, November 15, 2016 5:06 PM > To: Liu, Yong <yong.liu at intel.com> > Cc: dev at dpdk.org > Subject: Re: [dpdk-dev] [dpdk-announce] DPDK 16.11 released > > Hi and thanks for sharing your time constraints, > > 2016-11-15 01:46, Liu, Yong: > > As prospect for 17.02, our intel validation team have some concern about > > the release date. > > The official day off for Chinese Sprint Festival holiday will be from 27th > > Jan to 3th Feb. > > Most of our members may ask for more days leave either before or after the > > official day off. > > From our previous experience, it will take 3~4 weeks to do the full > > function and performance test. > > If the first candidate release in the middle of Jan, we can do first > > round of validation and raise issues to developers. > > The integration deadline is January 5. > So we can target/expect a RC1 on January 11. > > > And after the holiday, we can keep on the validation process and finish in > > two weeks. > > If release date is after Feb, it will be hard for us to cover all cases in > > release window. > > Yes, we must remind that mid-January is a hard deadline for RC1. > Then the release will be in mid-February to make sure you have some time > after the holidays. > What about Valentine's day? :)
