[RESULT][VOTE]: Release Apache OpenOffice 4.1.0 Beta (RC)
The vote period to release the AOO 4.1.0 Beta RC (based on release branch AOO410, revision 1573601) as Apache OpenOffice 4.1 Beta has ended. The ballot results in 26 votes, 26 +1 votes including 11 binding PMC member votes. 3 binding +1 votes are necessary for the release. That means the ballot closed successful to release the RC as AOO 4.1 Beta. Vote tally +1 Edwin Sharp +1 Olaf Felka (binding) +1 Sandyha Sivakumar +1 Steve Yin +1 Herbert Duerr (binding) +1 Andre Fischer (binding) +1 Oliver Rainer Wittmann (binding) +1 Kazunari Hirano +1 V Stuart Foote +1 Juergen Schmidt (binding) +1 Josef Latt +1 Jan Iversen (binding) +1 Raphael Bircher (binding) +1 Aivaras Stepukonis +1 tx99h4 (??) +1 Николай Нинков +1 Dirk Groskamp +1 Jeongkyu Kim +1 Markus Lange (binding) +1 Andrea Pescetti (binding) +1 Regina Henschel (binding) +1 Kay Schenk (binding) +1 Dave Barton +1 Rory O'Farrell +1 Sylvain Denis +1 Shengfeng Liu On 3/6/14 9:55 AM, Jürgen Schmidt wrote: Hi all, this is a call for vote on releasing the available release candidate (RC) as Apache OpenOffice 4.1.0 Beta. The Beta release is intended to reach more early adopters and to receive more valuable feedback to improve potentially critical areas for the final release. Apache OpenOffice 4.1 is a minor update with many bugfixes and at least 2 major improvements. It's the first version where we have the iAccessibility2 support integrated and available. A very huge step forward to reach and better support disabled users especially on Windows. The second improvement is the switch to 64 bit on MacOS. A long and overdue must do shift forward to support newer APIs (replace deprecated APIs) and platforms on MacOS. And we can provide again more complete UI translations and have now support for 37 languages. New languages for this release compared to 4.0.1 are Bulgarian, Danish, Hindi, Norwegian Bokmal and Thai. Apache OpenOffice 4.1 will be a further key milestone to continue the success of OpenOffice. An overview of release issues can be found under: http://people.apache.org/~jsc/developer-snapshots/snapshot/AOO4.1.0_Beta_fixes.html The release candidate artifacts (1) (source release, as well as binary releases for 37 languages) and further information how to verify and review Apache OpenOffice 4.1.0 Beta can be found on the following wiki page: https://cwiki.apache.org/confluence/display/OOOUSERS/Development+Snapshot+Builds The RC is based on the release branch AOO410, revision 1573601! And a fresh and clean RAT scan output of this revision can be found under http://people.apache.org/~jsc/developer-snapshots/snapshot/AOO4.1.0_RAT_Scan.html Please vote on releasing this package as Apache OpenOffice 4.1.0 Beta The vote starts now and will be open until: Sunday evening, 9 March: 2014-03-09 11:00pm UTC. But we invite all people to vote (non binding) on this RC. We would like to provide a release that is supported by the majority of our project members. [ ] +1 Release this package as Apache OpenOffice 4.1.0 Beta [ ] 0 Don't care [ ] -1 Do not release this package because... (1) the upload for the Linux 32 bit artifacts is still ongoing, but 64 bit is already available. - To unsubscribe, e-mail: qa-unsubscr...@openoffice.apache.org For additional commands, e-mail: qa-h...@openoffice.apache.org
Re: Please Review 4.1 Release Notes
The content in sections Performance Improvements/Enhancements and Bug Fixes are empty, should we remove the section Performance Improvements/Enhancements and add bug items in the section Bug Fixes? On Fri, Mar 7, 2014 at 9:40 PM, Rob Weir robw...@apache.org wrote: https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.1+Release+Notes I notice that the Release Notes say nothing about the IAccesible2 support. Shouldn't we have something there about it? Maybe mention what AT have been tested and work, and if there are any useful tips for users? Any other topics? The hope is to release the beta early next week. So it is important that we have good release notes for that. Regards, -Rob - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org -- Regards, Yu Zhen
[QA][Test Report] Weekly Status Update as of 20140310
Hi All, We continue doing the AOO 4.1 Function Verification test(FVT), here is the weekly update (2/25 - 3/10): *Test execution:* 1. Existing feature on 3 APP testing - Ongoing We have assigned 998(853 as of 2/14) test executions to about 42 volunteers, and completed about 56.0%(45.8% as of 3/10) in execution (654 test executions done, 535 as of 2/14). We have executed 120 test cases since Feb 14 with 3 more test execution volunteers. Total Not Run Passed Failed Blocked Completed [%] Debian Linux 64bit 56 7 36 10 3 87.5 MacOS X 209 81 95 20 7 61.24 Redhat Linux 32bit 69 66 1 2 0 4.35 Redhat Linux 64bit 277 121 110 42 4 56.32 Ubuntu Linux 64bit 167 37 95 30 5 77.84 Windows 7 209 102 82 22 3 51.2 Windows 8 182 101 62 19 0 44.51 Total 1169 515 481 145 22 56.0 *Defect summary:* 1. Complete verifcation for 44 resolved bugs which were identified to verify before beta candidate release, several reopened bugs are resolved and need verification again *Issues quality highlight:* 1. Apache OpenOffice 4.1 Beta(based on release branch AOO410, revision 1573601) is released after successfully votes 2. We do not complete FVT on schedule. From above execution statistic, the coverage on Linux, Mac and Windows is with balance, the low execution rate on Linux 32bit is not critical as low priority on platform Linux 32bit 3. We still need to run left test executions in FVT, especially on Windows 8 and Ubuntu 64 *Volunteer status:* 1. No new test execution volunteers(total 42 so far) joined on FVT execution work since Feb 14 2. Need defect volunteers to check regression bugs in Bugzilla *Plan for next week:* 1. Call for defect volunteers to check 4.1 regression bugs in Bugzilla 2. Continue to do FVT test on Mac, Linux and Windows 3. Remind some test execution volunteers to complete their assignments or do reassignment Thanks you all for effort this week, although we do not complete FVT on schedule, we really have some test execution volunteers participating actively and make progress day and day. Let's continue and work together to make preparation for beta release candidate! Regards, Yu Zhen
