>Feb ??, 2014 feature FVT finish (I know in China is public holiday as well from Jan 31 - Feb 7)
QA needs about 70 PD to complete the left 1061 executions (total 1061, suppose 15 executions per day per QA volunteer being concentrated on this work) on Writer(140), Calc(330) and Impress(591). We started the feature FVT early on Oct 29, the original plan is to complete Writer on 11/29, Calc on 12/27 and Impress on 1/24, we are very behind the planned schedule now because of the less volunteers. It would be optimistic to finish feature FVT before Feb 13. >Feb 21 - ? full regression testing and bug fixing Based on the experience from 4.0 Full Regression(22 QA volunteers completed 1,221 regression test executions during 10 weeks), if we take the same volume of executions and execution rate in 4.1, we may not complete it before Mar 20(4 weeks). The complete date would depend on how many QA volunteers will participate and how much effort they will provide, as well as how many defects are found. Regards, Yu Zhen On Tue, Dec 17, 2013 at 8:22 PM, Jürgen Schmidt <jogischm...@gmail.com>wrote: > Hi, > > well it seems that I was a little bit to optimistic or do I need a > break? I don't know probably both but I talked with the developers in my > direct surrounding field and taking the Christmas break, vacation etc. > into account we believe that my proposal was a little bit to optimistic. > > I don't know what others think but based on this new information I would > like to move my proposed schedule a little bit. > > Jan 24, 2014 feature freeze > Jan 27, 2014 translation freeze > Feb ??, 2014 feature FVT finish (I know in China is public holiday as > well from Jan 31 - Feb 7) > Feb 14, 2014 4.1 beta candidate > Feb 21, 2014 4.1 beta release for pubic review > Feb 21 - ? full regression testing and bug fixing > Mar 21, 2014 RC1? > Apr 1, 2014 GA? (I like this date if possible) > > It would nice to hear other opinions or general feedback. > > Juergen > > On 12/6/13 9:41 AM, Jürgen Schmidt wrote: > > Hi, > > > > some time ago we have discussed a language only release on base of > > 4.0.1. And even a language release requires a lot of work. Until today I > > see 3 potential languages ready which is not enough from my perspective. > > But on the other side we have some nice stuff in place that should be > > released asap, for example the iAccessibility support which is a great > > step forward and will help a lot of people. > > > > I would like to propose a new release AOO 4.1 early next year and as > > soon as possible. Taking into account that Christmas and the related > > holidays in many countries will slow down all the activities a little > > bit I can think of the following: > > > > Jan 10, 2014 features freeze > > Jan 13, 2014 translation freeze for beta > > Jan 20, 2014 feature FVT finish > > Jan 21, 2014 4.1 beta candidate, with major features and languages > > Jan 27, 2014 4.1 beta release for public review > > Jan 27 - ? full regression testing and bug fixing > > ? RC1 Feb 28, or later? > > GA ? > > > > > > I really would like to see the iAccessibility improvements publicly > > available as soon as possible because from my perspective it is a > > further huge milestone for AOO. And I would like to support the new > > languages as soon as possible and hopefully we can have a few more. Some > > are very close to be ready. > > > > Opinions and feedback is welcome and I hope may of you can share my view. > > > > Juergen > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > >
