2014-06-19 15:25 GMT+08:00 Jürgen Schmidt <[email protected]>: > On 19/06/14 03:55, Shenfeng Liu wrote: > > Hi, Juergen, > > > > > > 2014-06-18 19:18 GMT+08:00 Jürgen Schmidt <[email protected]>: > > > >> Hi, > >> > >> I am currently thinking about a possible release date for AOO 4.1.1 and > >> believe a date in August would be good. The main question is how long > >> the QA work will take? > >> > > > > I think August is a reasonable target date. > > I checked the testlink and found Yu Zhen already created AOO 4.1.1 test > > plan with test cases added. > > > > One question: when will we (or did we already?) create a 4.1.1 branch? > I'm > > asking because not only we need to input a build in testlink before we > can > > assign test cases to QA volunteers to start the test execution, but also > it > > can not be formally counted as 4.1.1 testing if performed on trunk build. > > We plan to work on the AOO410 branch and reuse it, we work a minor > bugfix release only. The released version are tagged and that's enough. > > I will upload a first dev build today or tomorrow > > That's great!
> > > > Thanks! > > > > > > > >> > >> AOO 4.1.1 will be a bugfix release only with some additional translation > >> update and potentially new languages. > >> > >> A further point is if we make a Beta or not or work with RC candidates > >> only. Again it is a bugfix release only and every official release (and > >> a Beta is official) needs more effort. And when I try to reflect the > >> last Beta I don't think it was very successful. We had >300000 downloads > >> and thought we would receive the necessary and good feedback we need to > >> release a good version. AOO 4.1 is good but we have some serious issues > >> that were not detected during normal Qa and not during the Beta phase of > >> active Beta users. > >> > > > > I agree that Beta is not necessary for AOO 4.1.1. > > > > > >> > >> Currently we have 26 issues with granted or requested showstopper flag. > >> Most of them are already fixed. > >> > > > > From QA perspective, the 4.1.1 testing can early start as soon as the 1st > > 4.1.1 build available. But we need to define a DCUT milestone, by which > > date, all the fixes are delivered to AOO 4.1.1 branch and no more patch > > will be accepted unless identified as blocking or 4.1.1 regression. Then > we > > can run the regression test after the DCUT to cover all impacted areas. > > we already in this mode and integrate only showstopper in the branch. > > We can align this with the translation deadline and after this date we > can start or continue with the regression testing > > Great! We can plan the testing accordingly. Thanks, Juergen! - Shenfeng (Simon) > Juergen > > > > > > > - Shenfeng (Simon) > > > > > > > > > >> > >> I haven't seen any issue so far a translation update. If issues exist > >> already please request the showstopper flag asap. > >> > >> We have no new strings and I know that update work or fixing of > >> translation is already ongoing. We should plan in time with a deadline > >> for translation updates. I think a possible date can be mid of July. We > >> need a fixed date that people can plan accordingly, otherwise we run > >> always in the same situation and changes are coming in late. But that > >> don't scale very well and we should keep deadlines in mind. > >> > >> What does others think about it? > >> > >> Juergen > >> > >> PS: this mail is on dev only because dev is our main mailing list. We > >> have again the situation that people active on QA or l18n don't read dev > >> which is problematic because they potentially miss important news for > >> upcoming releases. But sending info on all lists will result is split > >> discussion that I would like to avoid. I didn't really worked in the > >> past, even not with a reply-to filed. Well final deadlines will be > >> communicated on the qa@ and l18n@ list as well. > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: [email protected] > >> For additional commands, e-mail: [email protected] > >> > >> > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
