Re: [RELEASE][DISCUSS] How to download AOO 4.1.0 Beta?
On 2/18/14 9:19 PM, Marcus (OOo) wrote: Am 02/18/2014 08:44 AM, schrieb Andre Fischer: On 17.02.2014 20:44, Marcus (OOo) wrote: Am 02/17/2014 09:37 AM, schrieb Andre Fischer: On 14.02.2014 22:32, Rob Weir wrote: On Fri, Feb 14, 2014 at 3:53 PM, Marcus (OOo) marcus.m...@wtnet.de wrote: As this is our first beta release at Apache, I would like to clarify some things before it's maybe too late to change the facts and to prepare webpages: 1. Target group It is intended to be downloaded for the general public, right? 2. Hosting We are planning to host the files at Sourceforge, right? 3. File names: Of course the file names of the install files have to show a difference compared to the general release files. Suggestion: Apache_OpenOffice_4.1.0_Beta_Win_x86_install.exe *If* there is a need to publish another round, it could be extended with a number like: Apache_OpenOffice_4.1.0_Beta2_Win_x86_install.exe 4. Directory structure: Is it OK to expect to use the same dir structure like we have currently for 4.0.1? In general, yes, but please keep in mind that our Mac builds are now 64bit. I assume that the directories that contain the Mac downloads got renamed (Servers are currently down so I can not check). This is currently the complete path to the AOO 4.0.1 install files, example for English US: http://sourceforge.net/projects/openofficeorg.mirror/files/4.0.1/binaries/en-US/ There is no part included to reflect the OS and I don't know of an idea to do so. Or have I misunderstood you? Looks like I assumed wrong. I had the directory structure of the snapshot builds in mind, which obviously differ from that of the release. So we only keep in mind that the names of the Mac binaries change (not sure if that is relevant). That's true. Will keep in mind. It's nice that we talk about names and how to download but nobody took care about the technical realization. Which entries do we have to change to add a Beta string in the product name, about box, download files, etc. in way that we can install it in parallel and that everything works as expected. The whole process is once again not really intuitive and we have to figure it out. Many entries with more or less the same value and we have to check which one is used when and where ... Juergen Marcus The above makes sense to me. 5. Download webpage: Is it OK to expect to offer the download on our main download webpage? http://www.openoffice.org/download/ If yes, I can build up a download offer like we have for the green box. To ease the download as best as possible. I would not make this the default download option for users. We still want most users to download AOO 4.0.1. So keep the first box on /download.html as it is now. Maybe a yellow box (yellow == caution) with language that makes it clear that this is beta and gives the URL for reporting bugs. Were you thinking of a language/platform switch logic for the beta? Or just a link to a beta_other.html page with a table of links? If we do the table, then we would have room on the same page to give a prominent warning, a link to BZ, Release Notes, etc. Thanks! -Rob Thanks Marcus - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
[QA][Test Report] Weekly Status Update as of 20140224
Hi All, We continue doing the AOO 4.1 Function Verification test(FVT), here is the weekly update (2/15 - 2/24): *Test execution:* 1. Template validation - hold on, sent below issues and question to development Question: A new .odp is created with the template when try to open .otp file, is it intended? Issues: - only the first slide in template is available for apply to the existing presentation in AOO - It gets messed when apply template to an existing presentation 2. Existing feature on 3 APP testing - Ongoing We have assigned 853(817 as of 2/14) test executions to about 42(39 as of 2/14) volunteers, and completed about 45.8%(39.4% as of 2/14) in execution (535 test executions done, 461 as of 2/14). We get 3 more test execution volunteers since Feb 14 to speed up the test execution, we do not complete FVT as planned on Feb 24 TotalNot RunPassedFailedBlockedCompleted [%] Debian Linux 64bit5673610387.5 MacOS X209959020454.55 Redhat Linux 32bit69670202.90 Redhat Linux 64bit27712410941355.23 Ubuntu Linux 64bit167111479033.53 Windows 72091077722348.8 Windows 81821234415032.42 Total11696344031191345.8 *Defect summary:* 1. 46 resolved bugs are identified to verify before beta candidate release(Feb 28) (bug list is attached) *Issues quality highlight:* 1. 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 2. To release beta candidate safely, we need to verify proposed resolved bugs(total# = 46 so far) and check related function areas to see if any regression, will call for volunteers in community 3. We still need to run left test executions in FVT *Volunteer status: * 1. 3 new test execution volunteers(total 42 so far) joined on FVT execution work since Feb 14 2. Need defect volunteers to verify high priority bugs in Bugzilla (see above in Defect summary, any one can contribute on this, please let me know and provide the platforms you can help with) *Plan for next week:* 1. Verify identified high priority bugs 2. Continue to do FVT test on Mac, Linux and Windows 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 bugs-2014-02-24_Beta.ods Description: application/vnd.oasis.opendocument.spreadsheet - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
[URGENT] Re: [RELEASE]: new release branch AOO410 on trunk revision 1571426
Hi, On 25.02.2014 09:00, Jürgen Schmidt wrote: Hi, I create a new release branch for AOO410 based on trunk revision 1571426. Please use this branch for any AOO 4.1 relevant fixes. And make sure that the fix is merged to trunk as well (most developer fix it on trunk first and merge it on the branch). We start preparing a Beta RC on this new branch and will move in showstopper mode from now on. The same handling as before, nominate issues as showstopper by requesting the showstopper flag. When we are in 'showstopper mode' then the corresponding showstopper flag feature in our Bugzilla database must have been enabled. Can somebody with corresponding karma enable this feature? Thx in advance, Oliver. Juergen - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
[RELEASE] show stopper request: issue 124106
Hi, hereby I am requesting issue 124106 [1] to be considered as the showstopper for our 4.1.0 release. The issue has been fixed already on trunk. The fix assures a better import of *.docx documents created by Apples office suites, otherwise the import result is more or less not usefull. The made changes also fixes the import of the sample documents given at the issues 123702, 123761 and 124058. [1] https://issues.apache.org/ooo/show_bug.cgi?id=124106 Best regards, Oliver. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: How could I make a build on writer module?
I can see the sw library is inside the workdir, anyhow it is still not an executable. I'm just curious to know how could I run sw module in debug mode while fixing a defect so that I could understand whether my fix is correct. The worst is I'll never run an executable until I rebuild the installer and then install it into the system and test it from there. This is too costly as I'm just trying to verify my fix.
Re: How could I make a build on writer module?
On 25.02.2014 15:20, LOH KOK HOE wrote: I can see the sw library is inside the workdir, anyhow it is still not an executable. I'm just curious to know how could I run sw module in debug mode while fixing a defect so that I could understand whether my fix is correct. The worst is I'll never run an executable until I rebuild the installer and then install it into the system and test it from there. This is too costly as I'm just trying to verify my fix. Please have a look at https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO#Partial_Builds The general idea: a) Edit code in module sw/ b) Build sw c) Deploy sw libraries to your installed office d) Run soffice.bin in your debugger e) Find bug f) Go to a) -Andre - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Successful OpenOffice built
Hi :) First of all my operating system is Ubuntu 12.04 LTS 32-bit I think the things that were different from the building guide were some of the folders and files' names. The file used in including the configured environment has the name LinuxX86Env.Set.sh The folder which contains the files used for the setup process is named unxlngi6.pro also the file in that command sudo dpkg -i unxlngx6.pro/Apache_OpenOffice/deb/install/en-US/DEBS/desktop-integration/openoffice.org3.4-debian-menus_3.4-9593_all.deb was not named like that in my PC it was named openoffice4.0-debian-menus_4.0-9750_all.deb I used that building guide https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO/Step_by_step That is it :) I hope that that was useful :) On Monday, February 24, 2014 9:45 AM, Oliver-Rainer Wittmann orwittm...@googlemail.com wrote: :-) forgot the link to the building guide [1] https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO Best regards, Oliver On 24.02.2014 08:43, Oliver-Rainer Wittmann wrote: Hi, On 23.02.2014 00:36, Reem Elnagar wrote: Hi :) I managed to build Openoffice :) and it is written in the orientation to send you an e-mail when I finish so here it is :) cool. If you like you could share your experience. We are especially interested on the feedback, on how the building guide and the referenced sub pages for the different platforms [1] could be improved. Thx in advance. Best regards, Oliver. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
How could I linked the dependencies of soffice.bin?
I just make a build and the executable file (soffice.bin) was locate at /main/solver/410/unxlngx6.pro/bin. When I execute the file, it shows me: ./soffice.bin: error while loading shared libraries: libsofficeapp.so: cannot open shared object file: No such file or directory When I use `strace -f ./soffice.bin` command, I can see there are bunch of dependencies shown up. May I know how could I link these dependencies together if I execute soffice.bin directly? THanks @!
Re: How could I linked the dependencies of soffice.bin?
On 25.02.2014 15:46, LOH KOK HOE wrote: I just make a build and the executable file (soffice.bin) was locate at /main/solver/410/unxlngx6.pro/bin. When I execute the file, it shows me: ./soffice.bin: error while loading shared libraries: libsofficeapp.so: cannot open shared object file: No such file or directory What happens when you start soffice (without the .bin extension)? This is a script that sets some envirnment values that control (among other) where to look for the libraries. -Andre When I use `strace -f ./soffice.bin` command, I can see there are bunch of dependencies shown up. May I know how could I link these dependencies together if I execute soffice.bin directly? THanks @! - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
How to search for files to modify to fix a bug?
Hi all, I am just starting out to fix bugs. I spent some time around Bugzilla and now have a decent knowledge about how it works. And I understand finding the right files to fix is big part of fixing a bug. It seems there's no set of rules on how to find the files of interest. But, I bet there's some logical way to look for those files that needed to be modified to fix a bug. Any ideas/suggestions/advices on how to do that is much appreciated. Thanks, Tenzin - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Draft OpenOffice Writer Usability Survey
I while ago we were contacted by some academic researchers in Spain who wanted to do a usability study about OpenOffice Writer. The wanted to interview Writer users, both new and experienced. You can read about the study here: https://sites.google.com/site/silviateresitaacunna/Home/usability-in-oss Since data privacy would not allow us to give them our mailing list to contact the users directly, we came up with the idea of using an opt-in survey to collect the names of those who would be interested. You can see the draft survey here: http://survey.openoffice.org/index.php/396365/lang/en/ It collects basic info about the users and their experience level, and then at the end asks if they agree to participate in the follow-up study. If they agree then we collect their email address. If you get a chance, please review the survey and let me know of any concerns. Regards, -Rob - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Draft OpenOffice Writer Usability Survey
On Tue, Feb 25, 2014 at 4:51 PM, Rob Weir robw...@apache.org wrote: I while ago we were contacted by some academic researchers in Spain who wanted to do a usability study about OpenOffice Writer. The wanted to interview Writer users, both new and experienced. You can read about the study here: https://sites.google.com/site/silviateresitaacunna/Home/usability-in-oss Since data privacy would not allow us to give them our mailing list to contact the users directly, we came up with the idea of using an opt-in survey to collect the names of those who would be interested. You can see the draft survey here: http://survey.openoffice.org/index.php/396365/lang/en/ It collects basic info about the users and their experience level, and then at the end asks if they agree to participate in the follow-up study. If they agree then we collect their email address. If you get a chance, please review the survey and let me know of any concerns. The phrasing on the year questions, Each answer must be between 0 and 100, seems a bit odd, as if one is expected to give more than one answer to the question. Other than that it looks fine to me. Don
Re: [QA][Test Report] Weekly Status Update as of 20140224
On Tue, Feb 25, 2014 at 4:35 AM, Yuzhen Fan fanyuz...@gmail.com wrote: Hi All, We continue doing the AOO 4.1 Function Verification test(FVT), here is the weekly update (2/15 - 2/24): *Test execution:* 1. Template validation - hold on, sent below issues and question to development Question: A new .odp is created with the template when try to open .otp file, is it intended? Issues: - only the first slide in template is available for apply to the existing presentation in AOO - It gets messed when apply template to an existing presentation 2. Existing feature on 3 APP testing - Ongoing We have assigned 853(817 as of 2/14) test executions to about 42(39 as of 2/14) volunteers, and completed about 45.8%(39.4% as of 2/14) in execution (535 test executions done, 461 as of 2/14). We get 3 more test execution volunteers since Feb 14 to speed up the test execution, we do not complete FVT as planned on Feb 24 TotalNot RunPassedFailedBlockedCompleted [%] Debian Linux 64bit5673610387.5 MacOS X209959020454.55 Redhat Linux 32bit69670202.90 Redhat Linux 64bit27712410941355.23 Ubuntu Linux 64bit167111479033.53 Windows 72091077722348.8 Windows 81821234415032.42 Total11696344031191345.8 *Defect summary:* 1. 46 resolved bugs are identified to verify before beta candidate release(Feb 28) (bug list is attached) *Issues quality highlight:* 1. 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 2. To release beta candidate safely, we need to verify proposed resolved bugs(total# = 46 so far) and check related function areas to see if any regression, will call for volunteers in community 3. We still need to run left test executions in FVT *Volunteer status: * 1. 3 new test execution volunteers(total 42 so far) joined on FVT execution work since Feb 14 2. Need defect volunteers to verify high priority bugs in Bugzilla (see above in Defect summary, any one can contribute on this, please let me know and provide the platforms you can help with) *Plan for next week:* 1. Verify identified high priority bugs 2. Continue to do FVT test on Mac, Linux and Windows 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 - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org Is this still the correct URL for these outstanding/critical issues? https://issues.apache.org/ooo/buglist.cgi?cmdtype=doremlist_id=128088namedcmd=AOO_Need_Verify_4.1remaction=runsharer_id=249289 it seems like it is from the issues you attached above ... -- - MzK Cats do not have to be shown how to have a good time, for they are unfailing ingenious in that respect. -- James Mason
Re: Draft OpenOffice Writer Usability Survey
Rob Weir wrote: You can see the draft survey here: http://survey.openoffice.org/index.php/396365/lang/en/ I don't get the difference between being a University professor and being employed (or better: I don't see the reason to make separate categories for people who work at a University). More important: the last page should give some more information about the study, at least stating the topic (usability) in a more visible way. But linking to the study directly would be OK too. so people know what to expect. The rest is OK for me. Regards, Andrea. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Reporting a problem with the OpenOffice website
Greetings! On the on-line Help, the text is so small I can barely read it. Please include a zoom feature!! Really important with Calc, trying to check out the Functions. Thanks, Wayne, Happy User
Re: Draft OpenOffice Writer Usability Survey
It was fine to me. powered by android On Feb 25, 2014 4:37 PM, Andrea Pescetti pesce...@apache.org wrote: Rob Weir wrote: You can see the draft survey here: http://survey.openoffice.org/index.php/396365/lang/en/ I don't get the difference between being a University professor and being employed (or better: I don't see the reason to make separate categories for people who work at a University). More important: the last page should give some more information about the study, at least stating the topic (usability) in a more visible way. But linking to the study directly would be OK too. so people know what to expect. The rest is OK for me. Regards, Andrea. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
4.1.0_release_blocker granted: [Bug 124315] simple bootstrap doesn't work
j...@apache.org has granted 4.1.0_release_blocker: Bug 124315: simple bootstrap doesn't work https://issues.apache.org/ooo/show_bug.cgi?id=124315 - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
4.1.0_release_blocker granted: [Bug 124106] docx files created in Pages 5 are wrongly imported by AOO
j...@apache.org has granted Oliver-Rainer Wittmann o...@apache.org's request for 4.1.0_release_blocker: Bug 124106: docx files created in Pages 5 are wrongly imported by AOO https://issues.apache.org/ooo/show_bug.cgi?id=124106 --- Additional Comments from j...@apache.org grant showstopper flag - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
