Re: [Libreoffice-qa] [Moztrap] Some questions to the test cases, particularly #130
Hi Thomas, On Tue, Apr 02, 2013 at 06:02:52PM +0200, Thomas Hackert wrote: > > In English // steps > > > > Launch LibreOffice main program (vp. 1) > > Click on the "File" menu (vp. 2 vp. 3) > > > > In English // expected result > > > > 1. The welcome window should be appeared > > That is a different point, I nearly forgot ... :( IIRC the welcome > window only appears, when no LO was installed before, or am I wrong > ;? Thanks for your answer (and forwarding this mail to the dev ML as > well Thomas. Did you mean "splash screen", which is I usually called, with loading progress bar during launching LO? It disappears after LO loaded. The welcome window in test case means the first screen shown immediately after launching `libreoffice` without components (writer, calc, base etc.) opened. The screenshot explains it :) Best wishes, Yifan -- Yifan Jiang Libreoffice / SUSE Contact: yifan - irc.freenode.net/libreoffice = http://www.libreoffice.org/ http://www.documentfoundation.org/ <>___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice-qa] [Moztrap] Some questions to the test cases, particularly #130
Hi Devs, Sorry to interrupt, just to confirm, were you aware of some changes to the menu item File->Template (it seemed gone since 4.x)? The background is we were talking about vp.6 in a regression test case: http://manual-test.libreoffice.org/manage/cases/?&pagenumber=1&pagesize=20&sortfield=created_on&sortdirection=desc&filter-id=130 And if we ever removed the menu, we will update the test case as well. Thanks for your confirmative information:) Hi Thomas, Thanks for the thorough review of the testing :) Yes, I found the submenu seems gone on my 4.x build as well. The case may need update since it was written based on the 3.6.x build. Referring to your question, "vp" means "verify point", vp.1 appended to a step indicates the "expected result" will start with numbering 1, eg.: In English // steps Launch LibreOffice main program (vp. 1) Click on the "File" menu (vp. 2 vp. 3) In English // expected result 1. The welcome window should be appeared 2. These menu items should be activated: New, Open, Recent Documents, Wizards, Close, Templates, Exit Best wishes, Yifan On Tue, Apr 02, 2013 at 04:56:43AM +0200, Yifan Jiang wrote: > Good morning Yifan, *, > during my translation of the test cases in Moztrap into German, I > stumbled upon #130 > (http://vm12.documentfoundation.org/manage/case/130/). There I found > > Click on the mouse on the File -> Templates sub-menu and click on each > items inside (vp. 6) > > ... > > I have looked in my installed LO Version 4.0.2.2 (Build ID: > 4c82dcdd6efcd48b1d8bba66bfe1989deee49c3) as well as in Version 4.0.1.2 > (Build ID: 84102822e3d61eb989ddd325abf1ac077904985) under Debian Testing > AMD64, but have neither in my Germanophone UI nor when I switch the UI > to English such an entry in the menu ... :( I have only found one under > File -> New (in German: Datei -> Neu...). Now I am not sure, if this is > a relic from former versions (or from OOo times) or if you use a > different version or the like ... :( > > What version of LO (with what locale on your OS, which OS etc.) are you > using to create the test cases? Is there a difference to my > system/version? If not, could you correct the test and its expected > result? > > And I would like to see some native speakers of the English language to > proofread the test cases ... ;) Maybe my English is too bad and/or there > were some changes since my last lessons, but the example above sounds a > little bit strange to me* ... :( Do not get me wrong: I neither want to > be rude nor belittle your work at Moztrap, but should this not be > > Click on the File -> Templates sub-menu and click on each > item inside (vp. 6) > > instead? And as a final question: What does this "vp." mean? > > * This is not the only description, where I was wondering about the > wording ... ;) > > Sorry for the inconvenience and have a nice day > Thomas. > ___ > List Name: Libreoffice-qa mailing list > Mail address: libreoffice...@lists.freedesktop.org > Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa > Problems? > http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ > Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette > List archive: http://lists.freedesktop.org/archives/libreoffice-qa/ > -- Yifan Jiang Libreoffice / SUSE Contact: yifan - irc.freenode.net/libreoffice = http://www.libreoffice.org/ http://www.documentfoundation.org/ ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
need help for Android build.
Dear kind developers, I met a problem when trying to build LO Android libraries from the latest master, it stuck in early autogen.sh phase which looks something wrong with testing the cross compiler. I spent many time trying to see what happened but didn't figure out what's wrong :( I'd appreciate if any one can some give suggestions to resolve it, thank you in advance! --- ndk: android-ndk-r8b sdk: android-sdk_r20.0.1 gcc: 4.3.4 --- > ./autogen.sh running ./configure with 'CC_FOR_BUILD=gcc' 'CXX_FOR_BUILD=g++' '--with-android-ndk=/home/bench/android-ndk-r8b' '--with-android-sdk=/home/bench/android-sdk-linux' '--build=x86-unknown-linux-gnu' '--with-ant-home=/usr/share/ant' '--disable-zenity' '--disable-python' '--with-num-cpus=1' '--with-max-jobs=1' '--without-helppack-integration' '--without-myspell-dicts' * * Running LibreOffice build configuration. * checking build system type... x86-unknown-linux-gnu checking host system type... x86-unknown-linux-gnu checking for grep that handles long lines and -e... /usr/bin/grep checking for egrep... /usr/bin/grep -E checking for grep... (cached) /usr/bin/grep checking for sed... /usr/bin/sed checking for gawk... gawk checking for gawk... /usr/bin/gawk checking for bash... /bin/sh checking for GNU or BSD tar... tar checking for tar's option to strip components... --strip-components checking for ccache... /usr/bin/ccache configure: WARNING: ccache's cache size is less than 1GB using it is counter-producive: Disabling auto-ccache detection checking gcc home... /usr checking for gcc... /home/bench/android-ndk-r8b/toolchains/arm-linux-androideabi-4.4.3/prebuilt/linux-x86/bin /home/bench/android-ndk-r8b/toolchains/arm-linux-androideabi-4.6/prebuilt/linux-x86/bin/arm-linux-androideabi-gcc -march=armv7-a -mfloat-abi=softfp -mfpu=neon -Wl,--fix-cortex-a8 --sysroot /home/bench/android-ndk-r8b/platforms/android-9/arch-arm -L/home/bench/android-ndk-r8b/sources/cxx-stl/gnu-libstdc++/libs/armeabi-v7a checking for C compiler default output file name... configure: error: in `/windows/home/yifan/libo_solo': configure: error: C compiler cannot create executables See `config.log' for more details. Error running configure at ./autogen.sh line 187. --- Also, I tried to run the error section manually, which is failed as: /home/bench/android-ndk-r8b/toolchains/arm-linux-androideabi-4.6/prebuilt/linux-x86/bin/arm-linux-androideabi-gcc -march=armv7-a -mfloat-abi=softfp -mfpu=neon -Wl,--fix-cortex-a8 --sysroot /home/bench/android-ndk-r8b/platforms/android-9/arch-arm -L/home/bench/android-ndk-r8b/sources/cxx-stl/gnu-libstdc++/libs/armeabi-v7a /home/bench/android-ndk-r8b/toolchains/arm-linux-androideabi-4.6/prebuilt/linux-x86/bin/../lib/gcc/arm-linux-androideabi/4.6.x-google/../../../../arm-linux-androideabi/bin/ld: /lib/libz.so.1: no version information available (required by /home/bench/android-ndk-r8b/toolchains/arm-linux-androideabi-4.6/prebuilt/linux-x86/bin/../lib/gcc/arm-linux-androideabi/4.6.x-google/../../../../arm-linux-androideabi/bin/ld) /home/bench/android-ndk-r8b/platforms/android-9/arch-arm/usr/lib/crtbegin_dynamic.o: In function `atexit': crtbrand.c:(.text+0x44): undefined reference to `main' collect2: ld returned 1 exit status Best wishes, Yifan -- Yifan Jiang Libreoffice / SuSE Contact: yifan - irc.freenode.net/libreoffice = http://www.libreoffice.org/ http://www.documentfoundation.org/ ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: Local instance of Case Conductor
Hi Sophie, Thanks for the info, and I've set up a development environment and played a the CC for a while this week. Thanks for Petr and Thorsten's help, it could be possible for us to find somewhere to deploy so that people can play with it. One problem is the hardware resources, would you kindly help to get rough estimation from the Mozilla team that about recommended hardwares (memory, cpu, harddisk) for CC, in a scale of: - 200 test cases - 100 users - 20 users concurrency of running test The above data are extracted and a bit over estimated from our current Litmus system. Thanks in advance for your hlep :) Best wishes, Yifan On Thu, Apr 05, 2012 at 06:43:26PM +0200, Sophie Gautier wrote: > I'm in contact with the Mozilla team developing this application > since quite some time now, so don't hesitate to ask me directly if > you need anything from them. ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: Worked in OOo, doesn't load well in LibO
Hi Joop, Ye, I can see the most obvious problem in the title page, the text box and graphics in the header seems not aligned well. Besides this could be also a regression problem against 3.4.x. It is a typical problem to be reported in bugzilla, would you please refer to the wiki and report the bug: http://wiki.documentfoundation.org/BugReport Thanks~ Best wishes, Yifan On Mon, Mar 19, 2012 at 10:02:35PM +0100, Joop KIEFTE wrote: > Can anyone identify what's the problem in this document or in LibreOffice? > > Joop Kiefte > ___ > LibreOffice mailing list > LibreOffice@lists.freedesktop.org > http://lists.freedesktop.org/mailman/listinfo/libreoffice n nn ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
License Statement
Dear libreoffice, All of my past, present and future contributions to LibreOffice may be licensed under the MPL/LGPLv3+ dual license, including the go-oo (and where applicable, OpenOffice.org) code contributions. Best wishes, Yifan Jiang ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice] [Libreoffice-qa] QA ideas for 3.5 WAS Re: Improving the QA and Release for 3.5
Hi Cor, I hope I didn't interrupt anything :) But here's some of my comments. 1. Thanks for Rimas and Petr's actively participating, what we did in the past two month to improve the structure of Litmus and now the new stuff is online and a 3.5.0 beta regression test run is created, in which we are encouraging people to run the tests. https://tcm.documentfoundation.org/ There are a few important changes need to notify people, especially for l10n testers that: - we now have the localization test cases merged together with English cases, both in content and structure. Then we add "locale-dependent" property for each test case. https://tcm.documentfoundation.org/show_test.cgi?id=3105 Specifically, a test result submitted for a locale dependent cases will not influence the progress statistics of the test cases running in another locale condition. For a locale independent case,the executing result will be shared among all tests whatever locales were seleted. For locale selection I meant the bottom field here in test configuration details set: http://wiki.documentfoundation.org/File:Litmus_chose-de.png So it is important to make people informed correct locale selection is necessary before submitting test results. Also it is important to let l10n people know the translation version of test cases are not disappeared, all languages versions of test cases were just put together to save our effort depend on how much they related with languages. - we abandoned the build id selection to avoid duplicating test effort. So it is important to make people informed to actively use correct build submitting a result in the corresponding test run. For build id selection I also meant the field in configuration details set (the screenshot needs to update for this...): http://wiki.documentfoundation.org/File:Litmus_chose-de.png - we grouped test cases with priorities, and it is preferred the higher priority test cases are executed before lower ones. This can be seen when it comes to test group selection after the above configuration set. 2. We also got the wiki page updated and cleaned up. The important start pages to understand all related stuff can be: http://wiki.documentfoundation.org/Litmus http://wiki.documentfoundation.org/QA/Testing/Regression_Tests 3. As for the regression test plan, we got a full regression test related section in the QA processes page typically to describe what a Litmus admin should do when there comes a build: http://wiki.documentfoundation.org/QA/Processes#Full_regression_test_management Briefly speaking, we create a single test run for every beta and rc phases, during whose time slot the test cases inside test runs are supposed to be executed. For example, from the release plan, we will have 3 beta builds from 5/Dec to 9/Jan. In this phase, we do NOT create three test runs, instead the only test run "3.5.0 beta regression test" will be recommended there for nearly a month, when continuously submitting test result in the latest 3.5 beta build is expected. 4. Is it possible to emphasize the regression strategy in the bug hunting session you are planning? :) Not sure if some of the points answered your original question :) Please let me know if anyone needs more regression test and litmus related information! Thank you! Best wishes, Yifan On Tue, Dec 13, 2011 at 11:35:44PM +0100, Cor Nouws wrote: > Hi Petr, > > Cor Nouws wrote (09-12-11 13:44) > > >On the wiki, I added a section with the draft for the later to create > >separate wiki page: > >http://wiki.documentfoundation.org/QA/Improving_QA-Release-3.5#DRAFT_for_page_with_info_for_bug-hunting_session > > Is it possible for you - without wanting to stress you - to tell > smthg more about the expected planning? > > tjanks a lot > > ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice] Language dependent testing coverage you are interested.
Hi Stephan, I thinks they are great points! I'll add the outline of the case for this first. Thank you!:) Best wishes, Yifan On Wed, Nov 09, 2011 at 02:20:02PM +0100, Stephan Bergmann wrote: > korea.xcd enables the AutoCorrect - ReplaceSingleQuote setting > (which is otherwise disabled by default). This is apparently > designed to be enabled in a Korean locale. > > ctl.xcd sets the .../I18N/CTL/CTLFont configuration property to > true---no idea what effect that is supposed to have. Similarly > ctlseqcheck.xcd sets all the .../I18N/CTL/CTLSequenceChecking, > .../I18N/CTL/CTLSequenceCheckingRestricted, and > .../I18N/CTL/CTLSequenceCheckingTypeAndReplace configuration > properties to true. These are apparently designed to be enabled in > locales using complex text layout. > > Similarly, cjk.xcd sets various .../CJK configuration properties to > true (VerticalText, VerticalCallOut, Ruby, JapaneseFind, > EmphasisMarks, DoubleLines, CJKFont, ChangeCaseMap, and > AsianTypography; I assume those configuration properties control > whether the corresponding settings are made available in the UI for > configuration under "Tools - Options..."). It also sets to false > the Writer-specific configuration property > .../AutoFunction/Completion/Enable (and again, I have no idea what > effect that is supposed to have). > > Stephan > ___ > LibreOffice mailing list > LibreOffice@lists.freedesktop.org > http://lists.freedesktop.org/mailman/listinfo/libreoffice ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
[Libreoffice] Language dependent testing coverage you are interested.
Hi all, I was create more Language Dependent Testing Cases in our Litmus manual test cases management tool, and the items appended are some fields I ever concerned. Would you help share your ideas and the areas you are concerning which has a need of regression testing :) Thanks! - Spellcheck, Grammarcheck and Thesaurus - Hyphenation check - Templates - Help content - Eastern Asian language support - RTL specific problems Best wishes, Yifan ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice] lose circle charaters
Hi Yang, Thanks for your interests of contribution :) For the particular problem found, I suggest you firslty open a new bug with required information in freedesktop. The detailed guide of reporting a bug canbe found: http://wiki.documentfoundation.org/BugReport#LibreOffice_Bug_Reports Then to contribute your code, you may want to get more development information in: http://www.libreoffice.org/get-involved/developers/ http://wiki.documentfoundation.org/Development In addition, we have rich easy hacks list for your warm up excercise, from which you may try to clone the code base, build your libreoffice, get familiar with the part you are interested in, modify code and patch your fixes: http://wiki.documentfoundation.org/Easy_Hacks Finally, when meeting specific problems, #libreoffice-dev channel and the mailing list are always good places to ask :) Thanks! Best wishes, Yifan On Wed, Nov 09, 2011 at 11:54:05AM +0800, lianjing yang wrote: > hello everyone, > thank you for reading this email,i am a c++ developer, recently I met a > problem,i open a .doc which contains circle charaters on libreoffice,but it > lost all circle charaters.it is a bug,i would like to fix it ,but i have no > idea how to do and where to begin,can someone give me some idea ,thanks for > any reply! > > best wished > > Yang > ___ > LibreOffice mailing list > LibreOffice@lists.freedesktop.org > http://lists.freedesktop.org/mailman/listinfo/libreoffice ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice] [litmus] - buildid: "tag" no longer exists in 3.4 help -> About LibreOffice
Hi Petr, Is there a constant rule for checking the exact version from UI directly? For example, Help->About LibreOffice 3.4 340m1(Build:103) At the moment, it looks the Build:103 means 3.4.1 RC 3. Does it reliable enough? Thanks for help! Best wishes, Yifan On Sat, Jul 16, 2011 at 06:38:45PM +0200, gibi wrote: > Hello testers fellows, > > on litmus (for example here: > https://tcm.documentfoundation.org/run_tests.cgi?test_run_id=16) > The help on "More information about how to determine the build ID How do I > determine the build ID? " contains: > > > > To determine the LibreOffice build ID, go to Help ? About LibreOffice, and > look at the "tag" line. > > For example, |tag libreoffice-3.3.1.2| means that |libreoffice-3.3.1.2| is > your build ID. > > > > There is no more "tag" line in any of the 3.4 versionrc files ... at least > in linux-64 (I didn't check for Windows) > > Ok, I guess that the 3.4.2rc1 should be "libreoffice-3.4.2.1" but where > could we find the new build ID we should use to report in Litmus? > > It would be nice if a litmus admin could update the for > the 3.4 branch. > > Thanks a lot! > > > ___ > LibreOffice mailing list > LibreOffice@lists.freedesktop.org > http://lists.freedesktop.org/mailman/listinfo/libreoffice -- Yifan Jiang Libreoffice Contact: yifan - irc.freenode.net/libreoffice = http://www.libreoffice.org/ http://www.documentfoundation.org/ ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice] [ANN] LibreOffice 3.4.2 RC1 available
Hi, I've been running smoketest module on the build on SLED 11 sp1 i586, and tried to manually launch and did some random test. All pass :) Best wishes, Yifan On Thu, Jul 14, 2011 at 02:29:53PM +0200, Florian Effenberger wrote: > Hi *, > > for 3.4.2 rc1, we're now uploading builds to a public (but non-mirrored > - so don't spread news too widely!) place, as soon as they're available. > Grab them here: > > http://dev-builds.libreoffice.org/pre-releases/ > > If you've a bit of time, please give them a try & report *critical* bugs > not yet in bugzilla here, so we can incorporate them into the release > notes. Please note that it takes approximately 24 hours to populate the > mirrors, so that's about the time we have to collect feedback. > > The list of fixed bugs in this release is here: > > http://dev-builds.libreoffice.org/pre-releases/src/bugfixes-libreoffice-3-4-release-3.4.2.1.log > > So playing with the areas touched there also greatly appreciated - and > validation that those bugs are really fixed. > > NB: I'm jumping in for colleagues on vacation, but don't follow all > developer/release lists closely. In case there are major stoppers, > please Cc me into your reply. Thanks! > > Thanks a lot for your help, > Florian > ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice] Running smoketest module standalone.
Hi Caoln, Thanks for the ideas! The preferred goal is for option b, to make it able to run automatically without manual intervention. As an ideal result, we can have machines persistently check out the latest build and give back the testing results automatically. One question is I saw the smoketest.cxx seems handling the Macro security releasing on run time (Not sure my understanding is right), so is there specific reasons to extract the logic out (making another piece of code)? It could be the best if I can have things reusable at the current code base, so that we do not need to maintain 2 different code set for similar testing (I think some developers are also happy to use 'make check'). What is your concern about this aspect? Thanks a lot :) Best wishes, Yifan On Tue, Jul 12, 2011 at 11:57:06AM +0100, Caolán McNamara wrote: > On Tue, 2011-07-12 at 18:51 +0800, Yifan Jiang wrote: > > Hello all, > > > > I was working on extracting smoketestoo_native module out of the build > > system, > > to investigate the possibility running it with Libreoffice binary build. So > > that we could allow QA to run this quick test for a basic level of smoke > > testing with a released or pre-released build. > > You could try... > a) just grabbing the smoketest.sxw itself out of a build and manually > open it and click "run" after turning off macro protection. You don't > need any infrastructure to do that > b) extract out the logic that sets up a temp user dir with macro > protection already turned off in the settings and hack around passing > that to your installed set so that you can leave out clicking the "turn > off macro protection" step and dig out the command line invocation to > open and automatically run the macro in the smoketest.sxw without manual > intervention. > > a is super fast to do. > > C. > ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
[Libreoffice] Running smoketest module standalone.
Hello all,
I was working on extracting smoketestoo_native module out of the build system,
to investigate the possibility running it with Libreoffice binary build. So
that we could allow QA to run this quick test for a basic level of smoke
testing with a released or pre-released build.
Here is my findings with some questions, I would appreciate if any suggestions
or thinkings are provided.
[Running command]
The smoke test canbe run through a single line command for a specific
binary of libreoffice, provided with the argument -env:arg-soffice :
LD_LIBRARY_PATH=~/smoketest/lib:/opt/libreoffice3.4/ure/lib${LD_LIBRARY_PATH:+:${LD_LIBRARY_PATH}}
\
./cppunittester \
-env:UNO_SERVICES=file:///opt/libreoffice3.4/ure/share/misc/services.rdb \
-env:UNO_TYPES=file:///home/bench/smoketest/types.rdb \
-env:arg-soffice=path:/opt/libreoffice3.4/program/soffice \
-env:arg-user=./user \
-env:arg-env=LD_LIBRARY_PATH"${LD_LIBRARY_PATH+=$LD_LIBRARY_PATH}" \
-env:arg-testarg.smoketest.doc=~/smoketest/doc/smoketestdoc.sxw \
--protector ~/smoketest/lib/unoexceptionprotector.so
unoexceptionprotector ~/smoketest/lib/libsmoketest.so
where the ~/smoketest directory contains stuff outside the binary
packages. Namely, beside the libraries provided by ure pakcage, we may need
extra libraries and binary:
Binary:
cppunittester
Library:
libsmoketest.so
libtest.so
unoexceptionprotector.so
I also noticed the services.rdb delivered with ure binary package is Usable
for smoketest:
/opt/libreoffice3.4/ure/share/misc/services.rdb
However the types.rdb delivered with ure binary package will cause a Crash
when smoketesting:
* /opt/libreoffice3.4/ure/share/misc/types.rdb
Then I tried to copy the types.rdb from the master branch:
./unxlngi6.pro/bin/types.rdb
which works fine. Meanwhile, I found another type.rdb in the master build:
./unxlngi6.pro/bin/ure/types.rdb (similar with that in the one delived
in ure package)
whose size is quite smaller than that in the bin/, so I am not sure what's the
difference between them? Would you help me to understand it? Also please
correct me if anything I did is not in the right track. Thank you in advance!
Best wishes,
Yifan
--
Yifan Jiang
Libreoffice
Contact: yifan - irc.freenode.net/libreoffice
=
http://www.libreoffice.org/
http://www.documentfoundation.org/
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice] problem of master build cannot launch.
On Thu, Jul 07, 2011 at 04:31:36PM +0800, Yifan Jiang wrote: > Dear fellows, > > I met a startup problem with a newly pulled master HEAD since yesterday > (6/Jul). > > Firstly, I found smoketest fails on the HEAD (with error > officeconnection.cxx:140), then I tried to launch soffice.bin in solver/350 > manually, but soffice.bin crashes immedialy even before splash screen > appears. I tried again to confirm, actually, the splash screen did come out once, then crash. Sorry about the wrong description. Best wishes, Yifan ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
[Libreoffice] problem of master build cannot launch.
c10 in raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 #2 0xb7b64545 in abort () at abort.c:92 #3 0xb7d8dde3 in __gnu_cxx::__verbose_terminate_handler () at ../../../../libstdc++-v3/libsupc++/vterminate.cc:98 #4 0xb7d8b785 in __cxxabiv1::__terminate (handler= 0xb7d8dc90 <__gnu_cxx::__verbose_terminate_handler()>) at ../../../../libstdc++-v3/libsupc++/eh_terminate.cc:43 #5 0xb7d8b7c2 in std::terminate () at ../../../../libstdc++-v3/libsupc++/eh_terminate.cc:53 #6 0xb7d8b8fa in __cxxabiv1::__cxa_throw (obj=0x81456e8, tinfo=0xb7a1a52c, dest= 0xb79e70ce ) at ../../../../libstdc++-v3/libsupc++/eh_throw.cc:76 #7 0xb79e6a25 in cppu::loadSharedLibComponentFactory (rLibName=..., rPath= ..., rImplName=..., xMgr=..., xKey=..., rPrefix=...) at /windows/bootstrap/clone/ure/cppuhelper/source/shlib.cxx:382 #8 0xb79dc4ec in cppu::ORegistryFactoryHelper::createModuleFactory (this= 0x81452b8) at /windows/bootstrap/clone/ure/cppuhelper/source/factory.cxx:900 #9 0xb79dc802 in cppu::ORegistryFactoryHelper::createInstanceWithArgumentsAndContext (this=0x81452b8, rArguments=..., xContext=...) at /windows/bootstrap/clone/ure/cppuhelper/source/factory.cxx:800 #10 0xb48837a2 in stoc_smgr::OServiceManager::createInstanceWithArgumentsAndContext (this=0x805f898, rServiceSpecifier=..., rArguments=..., xContext=...) at /windows/bootstrap/clone/ure/stoc/source/servicemanager/servicemanager.cxx:1257 #11 0xb4882408 in stoc_smgr::OServiceManager::createInstanceWithArguments ( this=0x805f898, rServiceSpecifier=..., rArguments=...) at /windows/bootstrap/clone/ure/stoc/source/servicemanager/servicemanager.cxx:1313 #12 0xb7f59266 in desktop::Desktop::OpenSplashScreen (this=0xbfffe950) at /windows/bootstrap/clone/libs-core/desktop/source/app/app.cxx:3231 #13 0xb7f5e359 in desktop::Desktop::Main (this=0xbfffe950) at /windows/bootstrap/clone/libs-core/desktop/source/app/app.cxx:1584 #14 0xb6a79341 in ImplSVMain () at /windows/bootstrap/vcl/source/app/svmain.cxx:181 #15 0xb6a79478 in SVMain () at /windows/bootstrap/vcl/source/app/svmain.cxx:218 #16 0xb7f764e8 in soffice_main () at /windows/bootstrap/clone/libs-core/desktop/source/app/sofficemain.cxx:68 #17 0x08048bd4 in sal_main () at main.c:36 #18 main () at main.c:35 -- Yifan Jiang Libreoffice Contact: yifan - irc.freenode.net/libreoffice = http://www.libreoffice.org/ http://www.documentfoundation.org/ ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice] Litmus home page - link to tutorial is dead
Hi Sophie, That'd be wonderful! Thanks for taking care of this :) Best wishes, Yifan On Thu, Jul 07, 2011 at 08:06:57AM +0300, Sophie Gautier wrote: > Hi Yifan, all, > On 07/07/2011 05:21, Yifan Jiang wrote: >> Hi Rimas, >> >> Thanks for the nice info! I'll be able to merge them next week :) > > Yes, thanks a lot Rimas! I'll have the time to do it this afternoon, so you > don't have to care about it :) > > Kind regards > Sophie -- Yifan Jiang Libreoffice Contact: yifan - irc.freenode.net/libreoffice = http://www.libreoffice.org/ http://www.documentfoundation.org/ ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice] Litmus home page - link to tutorial is dead
Hi Rimas, Thanks for the nice info! I'll be able to merge them next week :) Best wishes, Yifan On Wed, Jul 06, 2011 at 06:47:52PM +0300, Rimas Kudelis wrote: > Hi all, > > > 2011.07.06 14:02, Yifan Jiang rašė: > > Thanks for noticing this :) > > > > Not sure if there is an official tutorial links, IMHO, we may want to make > > this as simple as one 'Get Help' link (rather than 3) to: > > > > http://wiki.documentfoundation.org/Litmus > > > > Then, we can add all of the stuff outside libreoffice (i.e Mozilla > > tutorials), > > to 'What is Litmus' sessions of our wiki page. > > > > Any other ideas? > > Yep, the links are dead upstream, it's not our problem. > > I've just found an archived version of the Litmus Tutorial: > http://web.archive.org/web/20071231151001/http://quality.mozilla.org/en/howto/litmus/tutorial > > Would anyone like to copy-paste it to our wiki? IMO, it would be much > easier to adapt already existing content to LibO than to write something > from scratch. > > There's also more content at > http://web.archive.org/web/20071224182737/http://quality.mozilla.org/en/howto/litmus, > and some currently available Litmus related content is listed on > http://quality.mozilla.org/docs/, in Litmus section. > > > Would you mind help to see if this could be a quick fix:) Thank > > you! > > Changing the links in the sidebar is indeed an easy fix. Just tell me > what links should be altered and how. > > Rimas > -- Yifan Jiang Libreoffice Contact: yifan - irc.freenode.net/libreoffice = http://www.libreoffice.org/ http://www.documentfoundation.org/ ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice] Litmus home page - link to tutorial is dead
Hi Cor, Thanks for noticing this :) Not sure if there is an official tutorial links, IMHO, we may want to make this as simple as one 'Get Help' link (rather than 3) to: http://wiki.documentfoundation.org/Litmus Then, we can add all of the stuff outside libreoffice (i.e Mozilla tutorials), to 'What is Litmus' sessions of our wiki page. Any other ideas? Hi Rimas, Would you mind help to see if this could be a quick fix:) Thank you! Best wishes, Yifan On Wed, Jul 06, 2011 at 09:32:56AM +0200, Cor Nouws wrote: > Hi Yifan, *, > > The subject says it all ;-) > > Hmm strange. the same link is used here too > https://wiki.mozilla.org/Litmus#Using_Litmus > > Regards, > > > ___ > LibreOffice mailing list > LibreOffice@lists.freedesktop.org > http://lists.freedesktop.org/mailman/listinfo/libreoffice -- Yifan Jiang Libreoffice Contact: yifan - irc.freenode.net/libreoffice = http://www.libreoffice.org/ http://www.documentfoundation.org/ ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice] Litmus testcase structure improvement.
Hi Cor, Thanks for spreading it! It is quite important we have a common sense on the working flow. I think your thinking is absolutely right and it is worth of taking time :) Thank you again! Best wishes, Yifan On Fri, Jul 01, 2011 at 07:36:12PM +0200, Cor Nouws wrote: > Hi Yifan > > Yifan Jiang wrote (30-06-11 12:51) >> That would be great :) Thanks! >> >> I commited some words (untested) here today for Litmus admin: >> >> http://wiki.documentfoundation.org/Litmus#Litmus_for_Libreoffice_Admin_Guide >> >> Please also let me know if something is confusing. > > For the moment - and the few spare minutes I found, I start to understand > it. > I will - again - mail to the Dutch list to see if others step in. >> btw. would you do the changes in 'Master Regression TC' branches, where all >> the latest test cases should be tracked:) > > Yes, that is clear and makes much sense. > But - noticing my current 'activity' here - you can imagine that much work > is not likely to be done by me. Sorry, but hey, don't let that be > discouraging. Anyone can stand up at any moment to help too :-) > > ATM for me most important is to understand it, so that I can point others > (Dutch NL group) to it, and give some guidance. > (For the rest, I try to keep on track with different releases, rc's, > sometimes nightly builds, etc and work in that and try to find/file bugs > when I come across something strange.) >> In addition, maybe the step by step working practice section 'Use case - >> Adding >> a new regression test case' would be helpful: >> >> http://wiki.documentfoundation.org/Litmus#Working_practices > http://wiki.documentfoundation.org/Litmus#Step_by_Step_Working_practices > > Will look to that next days! > > Regards, > > > ___ > LibreOffice mailing list > LibreOffice@lists.freedesktop.org > http://lists.freedesktop.org/mailman/listinfo/libreoffice -- Yifan Jiang Libreoffice Contact: yifan - irc.freenode.net/libreoffice = http://www.libreoffice.org/ http://www.documentfoundation.org/ ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice] Litmus testcase structure improvement.
Hi all, A bit update as follows: On Wed, Jun 22, 2011 at 02:41:57PM +0800, Yifan Jiang wrote: > TODO List I could think: > > 1. Litmus issue of test case manager access control (Thanks for Rimas is > working on that) > > 2. We need to find some place to store test samples attachment of test > cases (Need help, didn't follow up yet, maybe in git testing repo)? Thanks for petr's help, we can upload test cases to our git repo now: http://cgit.freedesktop.org/libreoffice/contrib/test-files/tree I'll follow up details later on. Any questions, feel free to ping. If you have any test samples for Litmus test cases to be upload and do not know how to handle it, please send it to me at this moment. Please make sure to tell which test cases are covered by the test samples. > 4. Update wiki I updated several sections for admin stuff: http://wiki.documentfoundation.org/Litmus It would be appreciated if you can have a review to see how clear it is. We may need more practical use cases: http://wiki.documentfoundation.org/Litmus#Step_by_Step_Working_practices Best regards, Yifan -- Yifan Jiang Libreoffice Contact: yifan - irc.freenode.net/libreoffice = http://www.libreoffice.org/ http://www.documentfoundation.org/ ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice] Litmus testcase structure improvement.
Hi Cor, That would be great :) Thanks! I commited some words (untested) here today for Litmus admin: http://wiki.documentfoundation.org/Litmus#Litmus_for_Libreoffice_Admin_Guide Please also let me know if something is confusing. btw. would you do the changes in 'Master Regression TC' branches, where all the latest test cases should be tracked:) In addition, maybe the step by step working practice section 'Use case - Adding a new regression test case' would be helpful: http://wiki.documentfoundation.org/Litmus#Working_practices Best wishes, Yifan On Thu, Jun 30, 2011 at 08:53:23AM +0200, Cor Nouws wrote: > Yifan Jiang wrote (30-06-11 06:44) >> Hi Sophie / all, >> [...] > > (just to let you know that I see the mails etc, and hope to be able to pick > up the next days - if not, it will be somewhere next week ..) > > > > ___ > LibreOffice mailing list > LibreOffice@lists.freedesktop.org > http://lists.freedesktop.org/mailman/listinfo/libreoffice -- Yifan Jiang Libreoffice Contact: yifan - irc.freenode.net/libreoffice = http://www.libreoffice.org/ http://www.documentfoundation.org/ ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice] Litmus testcase structure improvement.
Hi Sophie / all, The Master Regression TC and Master Feature TC branches are updated by separating Draw component and Impress. We are still seeking some one able to 'sync' content between German and English test cases. :) Best wishes, Yifan >> On Wed, Jun 29, 2011 at 05:51:56PM +0300, Sophie Gautier wrote: >> IMHO, The DE version test cases (which separate Impress and Draw test case >> groups) look more reasonable and easy to handle against combining Impress and >> Draw cases. >> >> Not sure if we had particular concerns to put the 2 set of cases together in >> English veresion (probably other languages version are derived from that)? So >> what's your opinion to: >> >> 1. divide Impress/Draw cases finally for all languages. >> >> 2. translate the incremental part of DE cases to English, then from >> English to all other languages :) > > Yes, and we should really get the same tests in every languages. > @the German group, please, if you add/modify tests, let us know so that we > can discuss and report the changes to get them for all the testers. Being > able to compare or check the same sets in all languages is part of the QA > and the overall quality of the process. > Thanks in advance :) > > Kind regards > Sophie -- Yifan Jiang Libreoffice Contact: yifan - irc.freenode.net/libreoffice = http://www.libreoffice.org/ http://www.documentfoundation.org/ ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice] Litmus testcase structure improvement.
On Wed, Jun 22, 2011 at 02:41:57PM +0800, Yifan Jiang wrote: > 3. In DE testgroup, the impress and draw are separated and they got more > cases than other languages. (Yifan will follow up this) Hi all, The difference is obvious to see in run report : https://tcm.documentfoundation.org/test_run_report.cgi?test_run_id=6 """ Subgroup: #DE - Impress Subgroup: #DE - Draw Subgroup: #EN - Impress & Draw Subgroup: #FR - Impress & Draw ... """ IMHO, The DE version test cases (which separate Impress and Draw test case groups) look more reasonable and easy to handle against combining Impress and Draw cases. Not sure if we had particular concerns to put the 2 set of cases together in English veresion (probably other languages version are derived from that)? So what's your opinion to: 1. divide Impress/Draw cases finally for all languages. 2. translate the incremental part of DE cases to English, then from English to all other languages :) Thanks! Best wishes, Yifan -- Yifan Jiang Libreoffice Contact: yifan - irc.freenode.net/libreoffice = http://www.libreoffice.org/ http://www.documentfoundation.org/ ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice] Litmus testcase structure improvement.
TODO List I could think: 1. Litmus issue of test case manager access control (Thanks for Rimas is working on that) 2. We need to find some place to store test samples attachment of test cases (Need help, didn't follow up yet, maybe in git testing repo)? 3. In DE testgroup, the impress and draw are separated and they got more cases than other languages. (Yifan will follow up this) 4. Update wiki (Not done/assigned yet). 5. We need feature test writing. I suggest it could be as simple as a link to somewhere else, or a brief sentence to tell clearly what the feature functions like and where to find it in user space :) Until the feature is as important as to be merged into Master Regression branch, we fulfil the case in detail. (need to start) Best wishes, Yifan ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
[Libreoffice] Litmus testcase structure improvement.
Edit current running branch's subgroup to link a new
case from the Master branch to the current running
one. (manage subgroups -> select Product as libreoffice
and Banch as currently running -> edit subgroups ->
manage testcases for this subgroup)
Please also let me know if things could be better.
--
Yifan Jiang
Libreoffice
Contact: yifan - irc.freenode.net/libreoffice
=
http://www.libreoffice.org/
http://www.documentfoundation.org/
--- Begin Message ---
Hi Jean-Baptiste,
Thanks for the nice ideas and suggestions! My comments as below.
Hi All,
This discussion is probably leading the next step we will adjust test case
management (Litmus) structure of Libreoffice, ideas and experience sharing
are welcome :) And I will summarize where we will go finally.
On Mon, Jun 13, 2011 at 01:54:46PM +0200, Jean-Baptiste Faure wrote:
> Le 13/06/2011 12:47, Yifan Jiang a écrit :
> Hi Yifan,
>
> I think we should do some simplifications in Litmus.
Yes! we need to adjust it to a more explicit way :)
> In fact I do not understand well how branches are supposed to work in
> Litmus. When you manage testcases and testgroups, you can see that there
> is no one in all branches but only in branch 3.3.1 (in Litmus meaning).
You are right, the branch information is from an relatively old test case set
(3.3.1). What I did for current runs is simply branch from an old test run
without touching test cases. So currently we have a simple set of testcases
reused everywhere. This actually needs to be improved.
> On the other hand when you manage the testruns you can see that each one
> contains the three testgroups defined in branch 3.3.1 (EN, DE and FR
> testgroups).
Ye, a bit confusing :)
> It seems to me that it would be more clear and easy to manage if we
> defined things as follows:
> - branches corresponding to x.y versions of LibreOffice: 3.3, 3.4, 3.5,
> and so on.
> - the branch x.y+1 would be defined by cloning the x.y branch and next
> adding new testcases needed by QA of the new functions implemented in
> the x.y+1 version.
My thinking is to:
1. have a relatively stable regression test case set which cover most
important function areas such as installation, launch, file open, save
etc.
2. have a changing feature cases (new functions) with the
evolution of Libreoffice builds. These cases can be various among
different Libreoffice build. And we can start testing features from beta
phase.
> - we manage RC and bugfix versions (x.y.1, x.y.2, etc.) only by creating
> dedicated testruns: there is no reason to change the testcases set when
> we pass from version x.y.0 to rc x.y.1 rc1 to bugfix x.y.1 to ... etc.
> So there is no reason to have a new branch for a new rc or bugfix
> - we need to define the buildID for each testrun, which does not seem to
> be the case at this moment.
Great idea! Actually we may not really want to have big change of regression
test cases set even between big versions as x.y and x.y+n.
A problem is if it is worth to repeatedly run regression cases in diffrent rc
builds unders the same big version? My initial thinking about this is to
define a rc test run for each minor version build, QA could run the tests
always on the corresponding latest rc build they have. This is based on the
assumptions:
1. code change between rc release would be safe
2. currently we have not enough resource to repeatedly run all regression
tests on each rc build.
But I guess it is not a big problem since when can always clone between rc
runs, the matter is how to define the run name. How about let us use 'rc' only
at very beginning and see if they are going well. Then we can expand the test
dedicating to specific rc builds if needed.
> According to that, we would have:
> - 2 branches 3.3 and 3.4
> - for the branch 3.3 :
> + one testrun 3.3.3-rc1
> + one testrun 3.3.3-rc2
> - for the branch 3.4 :
> + one testrun 3.4.0
> + one testrun 3.4.1-rc1
> + one testrun 3.4.1-rc2
> + etc.
> + one testrun 3.4.2-rc1
> + etc.
> - then a branch 3.5
> + etc.
Here is my thinking based on your proposal:
Take into consideration libreoffice build 3.3 and 3.4:
Branches:
- 3.3 Regression test branch (assuming it contains stable regression cases
written from scratch)
+ Test run - 3.3.0-rc regression test
+ Test run - 3.3.1-rc regression test
+ Test run - 3.3.2-rc regression test
...
- 3.3 New Feature test branch
+ Test run - 3.3 feature test ( new features in 3.3 build )
- 3.4 Regression test branch (containing stable regression cases, could be
Re: [Libreoffice] Need help on Litmus.
On Wed, Jun 15, 2011 at 12:00:58PM +0300, Rimas Kudelis wrote: > Hi Yifan, > yep, I have the same problem. I was told once how to edit Litmus to fix > this, but never got to it. I'll try to find that instruction and apply it > (this evening maybe), but for now, just grant those users global admin > rights. > > Rimas > Hi Rimas, Thanks for the quick response! Since we are just starting to take this running, I think the time is sufficient to awaiting your nice adjustment :) To fix it, please let me know if you need any help from me! Thank you ! Best wishes, Yifan -- Yifan Jiang Libreoffice Contact: yifan - irc.freenode.net/libreoffice = http://www.libreoffice.org/ http://www.documentfoundation.org/ ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
[Libreoffice] Need help on Litmus.
Hello Rimas, I am writing to search for your help about user management on Litmus. The wiki of Litmus but didn't give me a hint :( Since there may be more people want to contribute to manage test cases in Litmus, so I tried to have a look at if the access control works as expected. First I set up a dummy (yifanj), then I tried a bit to set my dummy (yifanj) role to 'Litmus Test Run/Test Day Administrators', after that, use yifanj to login. The admin links are located correctly on the left hand panel. But when I click them, the existing testcases, groups, subgroups, branches etc. information are not 'readable' as empty, thus they cannot be used or edited. For example, using my dummy: - click 'manage testcases', - click 'Product' list box, => There's nothing inside (there should be a Libreoffice product there) Another example: - click 'manage categories', => the 'existing branches' list is also empty So it could be an obstacle for the case administrator to manage existing stuff, which is strange. I see your id is in the 'Litmus Test Run/Test Day Administrators' as well, do you see the same thing? Is it something buggy or I did wrong? I appreciate if you can help, thank you :) Best wishes, Yifan -- Yifan Jiang Libreoffice Contact: yifan - irc.freenode.net/libreoffice = http://www.libreoffice.org/ http://www.documentfoundation.org/ ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice] QA-hints ? -> question for devs !
Hi Jean-Baptiste, Thanks for the nice ideas and suggestions! My comments as below. Hi All, This discussion is probably leading the next step we will adjust test case management (Litmus) structure of Libreoffice, ideas and experience sharing are welcome :) And I will summarize where we will go finally. On Mon, Jun 13, 2011 at 01:54:46PM +0200, Jean-Baptiste Faure wrote: > Le 13/06/2011 12:47, Yifan Jiang a écrit : > Hi Yifan, > > I think we should do some simplifications in Litmus. Yes! we need to adjust it to a more explicit way :) > In fact I do not understand well how branches are supposed to work in > Litmus. When you manage testcases and testgroups, you can see that there > is no one in all branches but only in branch 3.3.1 (in Litmus meaning). You are right, the branch information is from an relatively old test case set (3.3.1). What I did for current runs is simply branch from an old test run without touching test cases. So currently we have a simple set of testcases reused everywhere. This actually needs to be improved. > On the other hand when you manage the testruns you can see that each one > contains the three testgroups defined in branch 3.3.1 (EN, DE and FR > testgroups). Ye, a bit confusing :) > It seems to me that it would be more clear and easy to manage if we > defined things as follows: > - branches corresponding to x.y versions of LibreOffice: 3.3, 3.4, 3.5, > and so on. > - the branch x.y+1 would be defined by cloning the x.y branch and next > adding new testcases needed by QA of the new functions implemented in > the x.y+1 version. My thinking is to: 1. have a relatively stable regression test case set which cover most important function areas such as installation, launch, file open, save etc. 2. have a changing feature cases (new functions) with the evolution of Libreoffice builds. These cases can be various among different Libreoffice build. And we can start testing features from beta phase. > - we manage RC and bugfix versions (x.y.1, x.y.2, etc.) only by creating > dedicated testruns: there is no reason to change the testcases set when > we pass from version x.y.0 to rc x.y.1 rc1 to bugfix x.y.1 to ... etc. > So there is no reason to have a new branch for a new rc or bugfix > - we need to define the buildID for each testrun, which does not seem to > be the case at this moment. Great idea! Actually we may not really want to have big change of regression test cases set even between big versions as x.y and x.y+n. A problem is if it is worth to repeatedly run regression cases in diffrent rc builds unders the same big version? My initial thinking about this is to define a rc test run for each minor version build, QA could run the tests always on the corresponding latest rc build they have. This is based on the assumptions: 1. code change between rc release would be safe 2. currently we have not enough resource to repeatedly run all regression tests on each rc build. But I guess it is not a big problem since when can always clone between rc runs, the matter is how to define the run name. How about let us use 'rc' only at very beginning and see if they are going well. Then we can expand the test dedicating to specific rc builds if needed. > According to that, we would have: > - 2 branches 3.3 and 3.4 > - for the branch 3.3 : > + one testrun 3.3.3-rc1 > + one testrun 3.3.3-rc2 > - for the branch 3.4 : > + one testrun 3.4.0 > + one testrun 3.4.1-rc1 > + one testrun 3.4.1-rc2 > + etc. > + one testrun 3.4.2-rc1 > + etc. > - then a branch 3.5 > + etc. Here is my thinking based on your proposal: Take into consideration libreoffice build 3.3 and 3.4: Branches: - 3.3 Regression test branch (assuming it contains stable regression cases written from scratch) + Test run - 3.3.0-rc regression test + Test run - 3.3.1-rc regression test + Test run - 3.3.2-rc regression test ... - 3.3 New Feature test branch + Test run - 3.3 feature test ( new features in 3.3 build ) - 3.4 Regression test branch (containing stable regression cases, could be cloned from 3.3 and did some improvement) + Test run - 3.4.0-rc regression test + Test run - 3.4.1-rc regression test + Test run - 3.4.2-rc regression test ... - 3.4 New Feature test branch + Test run - 3.4 feature test ( new features in 3.4 build ) > I think we need to agree on the general organization before > that the system has become too big and too widely used. > I can do these modifications if we have a general agreement. > As that assume to remove several branches and to rebuild testruns, it
Re: [Libreoffice] QA-hints ? -> question for devs !
On Mon, Jun 13, 2011 at 11:47:18AM +0200, Petr Mladek wrote: > Also Sophie and Yi Fan are trying to organize testing of beta and rc > builds. There is used Litmus server to coordinate the work between the > various testers. I am sure that they are looking for more testers and > test case writers. Hi Cor, Great thanks for the message! Sorry I overlooked your mail at first glance, our regression testing is organized here: https://tcm.documentfoundation.org/ Here is the instruction how to contribute on running test on it: http://wiki.documentfoundation.org/Litmus I am probably going to deliver some important new cases or coverage areas to the mailing list for review/discuss this week, please keep tuned and let me know if you have any ideas about this or about QA. Also please do not hesitate to let us know if any questions. We are looking forward to you :) Best wishes, Yifan -- Yifan Jiang Libreoffice Contact: yifan - irc.freenode.net/libreoffice = http://www.libreoffice.org/ http://www.documentfoundation.org/ ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice] [REVIEW] missing desktop icons (fdo#37160)
On Mon, May 16, 2011 at 09:17:07PM +0200, Petr Mladek wrote: > Hi, > > could you please review the attached patch for LO-3.4? > > LO-3.4 can be installed in parallel with LO-3.3 on Linux (fdo#36551). Hi Petr, If this is a new feature, shall we release note it to spread the word? :) Thanks! http://wiki.documentfoundation.org/ReleaseNotes/3.4 Best wishes, Yifan ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
[Libreoffice] A 3.4 Feature question.
Hi Kohei, When reviewing and testing the feature in: http://wiki.documentfoundation.org/ReleaseNotes/3.4 This one looks has several regression bugs fixed, do we have a list of bug ids to verify? Thanks! * Re-work of the internals: The internal implementation of DataPilot has been significantly re-worked in order to fix several regressions especially with regard to refreshing of DataPilot tables. Best wishes, Yifan -- Yifan Jiang Libreoffice Contact: yifan - irc.freenode.net/libreoffice = http://www.libreoffice.org/ http://www.documentfoundation.org/ ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice] Compilation failed in vcl module (warning treated as errors)
Hi Joseph, Thanks for the hint, it works now :) Best wishes, Yifan On Wed, May 11, 2011 at 05:23:20AM -0700, Joseph Powers wrote: > > On May 11, 2011, at 12:24 AM, Yifan Jiang wrote: > > > GetActionCount > > = main repo = > = artwork = > = base = > = calc = > sc/source/ui/drawfunc/futext3.cxx:bNewNote = > (pCalcUndo->GetActionCount() > 0) && pCalcUndo->GetAction( 0 )->ISA( > SdrUndoNewObj ); > = components = ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
[Libreoffice] Patch review: remove g_mediaplayer testcase dependency for JMF.
Hi, The testautomation case g_mediaplayer.inc looks never running on purpose because of lack of JMF. So I removed this dependency and the test seems working fine. Would you have a review? Thanks! -- Yifan Jiang Libreoffice Contact: yifan - irc.freenode.net/libreoffice = http://www.libreoffice.org/ http://www.documentfoundation.org/ >From 21895532e78da95eaa6c2a163b0bb60e675d4ff0 Mon Sep 17 00:00:00 2001 From: Yifan Date: Mon, 9 May 2011 17:32:36 +0800 Subject: [PATCH] remove JMF dependency in test case --- .../optional/includes/global/g_mediaplayer.inc | 56 +--- 1 files changed, 26 insertions(+), 30 deletions(-) diff --git a/testautomation/graphics/optional/includes/global/g_mediaplayer.inc b/testautomation/graphics/optional/includes/global/g_mediaplayer.inc index f78cdf8..e3e824a 100644 --- a/testautomation/graphics/optional/includes/global/g_mediaplayer.inc +++ b/testautomation/graphics/optional/includes/global/g_mediaplayer.inc @@ -39,13 +39,9 @@ testcase g_mediaplayer dim timevalue2 dim timevalue3 dim timecounter, iWaitIndex, timefound as integer - + if iSprache <> 39 then Printlog "- MediaPlayer" -if gPlatgroup = "unx" then - QaErrorLog "Solaris / Linux: Soundcard + Java Media Framework (JMF) Media-Libraries is needed." - goto endsub -endif Datei$ = ConvertPath (convertPath (gTesttoolPath + "graphics\required\input\29secsound.wav")) printlog "Open New Document" Call hNewDocument @@ -53,12 +49,12 @@ testcase g_mediaplayer printlog "Check if the Media Player already exists - if so - close it" kontext "mPlayer" printlog "Close the MediaPlayer if it is open already" -if mPlayer.exists then +if mPlayer.exists then warnlog "The MediaPlayer was visible since some earlier test." ToolsMediaPlayer printlog "Closed the Media Player" endif - + printlog "Tools - MediaPlayer" ToolsMediaPlayer sleep 2 @@ -76,11 +72,11 @@ testcase g_mediaplayer kontext "OeffnenDlg" Pfad.SetText Datei$ Oeffnen.Click - + printlog "This test wont work correctly under Solaris and Linux," printlog "unless some optional Media-libraries are installed." printlog "Therefore we warn the tester about it if we cannot open the file." - + iWaitIndex = 0 do while OeffnenDlg.Exists AND iWaitIndex < 10 sleep (1) @@ -93,15 +89,15 @@ testcase g_mediaplayer kontext "Mplayer" ToolsMediaPlayer printlog "close document" - Call hCloseDocument + Call hCloseDocument goto endsub else kontext "Mplayer" if Mplayer.exists then printlog "Media Player was opened." endif - + timevalue1 = mTimeedit.GetText - + printlog "Stop" sleep 2 mStop.Click @@ -144,7 +140,7 @@ testcase g_mediaplayer else Printlog "the play-button seemed to work. Good." endif - + printlog "Pause" mPlay.Click sleep 10 @@ -159,10 +155,10 @@ testcase g_mediaplayer else Printlog "the pause-button seemed to work. Good." endif - + printlog "Time" printlog " Click Stop to get to the beginning." -mStop.Click +mStop.Click sleep 1 printlog "And make sure it's really the beginning." timevalue1 = mTimeedit.GetText @@ -173,13 +169,13 @@ testcase g_mediaplayer else printlog "Sound stopped, time-value set to 00:00:00." endif - + printlog "We press 'Play'" printlog "Click play to get it running" -mPlay.Click +mPlay.Click sleep 5 timefound = 0 - + for timecounter = 1 to 5 timevalue1 = mTimeedit.GetText if timevalue1 = "00:00:20 / 00:00:29" then @@ -191,7 +187,7 @@ testcase g_mediaplayer timefound = 2 endif next timecounter - + if timefound = 1 then Printlog "the time-counter seemed to work. Good." elseif timefound = 2 then @@ -199,34 +195,34 @@ testcase g_mediaplayer elseif timefound = 0 then warnlog "Either the time didnt change, or the test-computer is too fast." endif - + printlog &qu
Re: [Libreoffice] Compilation failed in vcl module (warning treated as errors)
Hi Mikos/Joseph, I met a similar problem when: $ cd tail_build $ make -r ... bootstrap/sw/source/filter/ww1/w1filter.cxx: In member function ‘void Ww1Picture::Out(Ww1Shell&, Ww1Manager&)’: bootstrap/sw/source/filter/ww1/w1filter.cxx:1914: error: ‘class GDIMetaFile’ has no member named ‘GetActionCount’ bootstrap/solver/300/unxlngi6.pro/workdir/CxxObject/sw/source/filter/ww1/w1filter.o] Error 1 On Wed, May 11, 2011 at 03:36:47AM +0200, Miklos Vajna wrote: > On Tue, May 10, 2011 at 11:20:05PM +0200, Julien Nabet > wrote: > > Compiling: vcl/source/gdi/gdimtf.cxx > > /home/maryline/compile-libreoffice/libo/clone/libs-gui/vcl/source/gdi/gdimtf.cxx:296:13: > > > > error: prototype for 'MetaAction* > > GDIMetaFile::ReplaceAction(MetaAction*, size_t)' does not match any in > > class 'GDIMetaFile' > > ../../inc/vcl/gdimtf.hxx:218:21: error: candidate is: MetaAction* > > GDIMetaFile::ReplaceAction(MetaAction*, sal_uLong) > > (...) > > > Since I didn't fully understand how and when to use "sal_uLong" and > > "size_t" + their implementation with 32/64 bits, I don't know how to > > fix this. > > Looks like Joseph started to replace sal_uLong by size_t, but he did not > lave the prototypes / implementations in sync, see commit 6fb23043. > > I wonder how did this even build for him. ;) > > Norbert already fixed a few, issues, I've fixed > GDIMetaFile::ReplaceAction() header, GDIMetaFile::Play() implementation > and GDIMetaFile::GetActionPos() implmenentation, now it at least builds > here. > > > By the way, couldn't it be useful to use --enable-werror by default ? > > See here: > http://blog.flameeyes.eu/2009/02/25/future-proof-your-code-dont-use-werror > > Of course I have no problem with enabling werror by default when > building from git, but doing it in release tarballs sounds odd. > ___ > LibreOffice mailing list > LibreOffice@lists.freedesktop.org > http://lists.freedesktop.org/mailman/listinfo/libreoffice -- Yifan Jiang Libreoffice Contact: yifan - irc.freenode.net/libreoffice = http://www.libreoffice.org/ http://www.documentfoundation.org/ ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice] QA process
On Wed, Apr 27, 2011 at 05:57:39PM +0300, Sophie Gautier wrote: >> --->8- >> Hi Sophie / Petr and all, >> >> Thanks for the comments and ideas! I updated several wiki pages today to >> outline what we got through the discussion. Please would you have a review >> and >> feedback is appreicated :) > > Did you locked the QA pages on the wiki, it seems I can't edit them even > when logged? Weird, I didn't open/edit the page ;-) Is this a constant problem? > Tomorrow I'll run the testtool on Windows and Linux, to check if every > thing is ok on this part too (enough details for new comers mostly). > As you may have seen, I'm also planing a new IRC QA session targeted on RC > time and tests. But I'll keep the list update on the progress of > organization. Great! Please let me know if anything is not working/strange. Best regards, Yifan -- Yifan Jiang Libreoffice Contact: yifan - irc.freenode.net/libreoffice = http://www.libreoffice.org/ http://www.documentfoundation.org/ ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice] QA process
Hey Sophie, Thanks for mentioning it :) I have ever sent a process document to wiki in the mid of the month (13/Apr or so). The content attached as follows as well. It would be great if you have a review if time. Best wishes, Yifan --->8- Hi Sophie / Petr and all, Thanks for the comments and ideas! I updated several wiki pages today to outline what we got through the discussion. Please would you have a review and feedback is appreicated :) Details comes with: 1. Re-structure of QA page to put stuff into proper process. http://wiki.documentfoundation.org/QA I also updated the function test process part. From my understanding of comments, Native Language QA is not considered as a single process since what could be done is quite similar with Function QA, except that Native Language QA may have different Test build and Test cases (though maybe part of overlapping with) from function test. L10n process is empty since it seems to be a different one. 2. Update the QA-team to outline a Test maintenance team: http://wiki.documentfoundation.org/QA/QA_Team 3. Update a bit the BugReport Details page to put 'Severity' for concerning: http://wiki.documentfoundation.org/BugReport_Details The severity stuff is simply extracted from fdo documentation, we may want to define them in more detail. About the priority setting, I double checked the fdo documentation https://bugs.freedesktop.org/page.cgi?id=fields.html#importance which shows 'This field is utilized by the programmers/engineers to prioritize their work to be done.'. In our case, not every bugs are assigned when they are reported/triaged. So let me confirm we would like this to be done in bug triage phase for not losing those high priority bugs at the first time, though assigned developers can do further adjustment via his/her own work states. --->8--------- -- Yifan Jiang Libreoffice Contact: yifan - irc.freenode.net/libreoffice = http://www.libreoffice.org/ http://www.documentfoundation.org/ ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice] Libreoffice QA process outline - a coarse draft.
> > Collect the results on the wiki may be more easier for every body to > > participate. > > It might be enough to show them in Litmus if they are well visible > there. It looks a report page for a specific run can be generated as: https://tcm.documentfoundation.org/test_run_report.cgi?test_run_id=3 Clicking the last column with non-zero inside would show the detailed result. Is it good enough for sharing info between QA team and release team? Best regards, Yifan ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice] Libreoffice QA process outline - a coarse draft.
Hi Sophie / Petr and all, Thanks for the comments and ideas! I updated several wiki pages today to outline what we got through the discussion. Please would you have a review and feedback is appreicated :) Details comes with: 1. Re-structure of QA page to put stuff into proper process. http://wiki.documentfoundation.org/QA I also updated the function test process part. From my understanding of comments, Native Language QA is not considered as a single process since what could be done is quite similar with Function QA, except that Native Language QA may have different Test build and Test cases (though maybe part of overlapping with) from function test. L10n process is empty since it seems to be a different one. 2. Update the QA-team to outline a Test maintenance team: http://wiki.documentfoundation.org/QA/QA_Team 3. Update a bit the BugReport Details page to put 'Severity' for concerning: http://wiki.documentfoundation.org/BugReport_Details The severity stuff is simply extracted from fdo documentation, we may want to define them in more detail. About the priority setting, I double checked the fdo documentation https://bugs.freedesktop.org/page.cgi?id=fields.html#importance which shows 'This field is utilized by the programmers/engineers to prioritize their work to be done.'. In our case, not every bugs are assigned when they are reported/triaged. So let me confirm we would like this to be done in bug triage phase for not losing those high priority bugs at the first time, though assigned developers can do further adjustment via his/her own work states. Best wishes, Yifan ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
[Libreoffice] Libreoffice QA process outline - a coarse draft.
Bug Triager's job - We may need a priority setting guide similar to release criteria. Do we have it already somewhere? -- Yifan Jiang Libreoffice Contact: yifan - irc.freenode.net/libreoffice = http://www.libreoffice.org/ http://www.documentfoundation.org/ ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice] Libreoffice QA Review and Feedback Gathering - Title mail
Thanks Petr and Sophi, I've got the bug triage process a bit updated in the section Process 5.2: http://wiki.documentfoundation.org/BugTriage Best regards, Yifan On Fri, Apr 01, 2011 at 04:18:49PM +0200, Petr Mladek wrote: > Yifan Jiang píše v Pá 01. 04. 2011 v 15:40 +0800: > > Bug Triage: > > > > - Looking for people as Focal Points for handling bugs written in > > non-English. > > > > The role of focal points people is to help ping NL/l10n team asking > > for a bug translation. > > > > Before that, we could assign those bug to Sophi at the moment, we may > > indicate these somewhere in wiki ;-) > > I have updated Sophi's expertise at > http://www.freedesktop.org/wiki/Software/LibreOffice/FindTheExpert ;-) > > Best Regards, > Petr > -- Yifan Jiang Libreoffice Contact: yifan - irc.freenode.net/libreoffice = http://www.libreoffice.org/ http://www.documentfoundation.org/ ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice] Libreoffice QA Review and Feedback Gathering - Title mail
Hey all, Just had a nice talk with Sophi, here is the conversation summary: QA People: - Look forward to having more people on the list in 15/Apr IRC session. Bug Triage: - Looking for people as Focal Points for handling bugs written in non-English. The role of focal points people is to help ping NL/l10n team asking for a bug translation. Before that, we could assign those bug to Sophi at the moment, we may indicate these somewhere in wiki ;-) Manual and Localization Testing: - The most important thing is making Litmus running more reliably. We have a willing to move most of the QA work to the system. It would be nice we all follow the same process starting from 3.4 QA. Sophi will check the Litmus deployment with Rimas. - Sophi will contact with people to see if they are working on a general process of testing. Yifan will scratch an outline if nobody is doing it. Yifan is also interested in helping that done. Automation Testing: - We knew more people who is doing testtool automation work, we'll connect to them. - We need to figure out a way to put the testtool logs. Possibly include this for Litmus management as well. - Yifan can be one of the testool automation script maintainers: http://wiki.documentfoundation.org/QA/QA_Team#QA_Team_volunteers_in_alphabetic_order -- Yifan Jiang Libreoffice Contact: yifan - irc.freenode.net/libreoffice = http://www.libreoffice.org/ http://www.documentfoundation.org/ ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
[Libreoffice] Libreoffice QA Review and Feedback Gathering - Automation Testing
[Automation Testing] + Related wiki: http://wiki.documentfoundation.org/QA/Testing/Using_Testtool 1. Currently this page has got HOWTO of Windows version of testtool, I will update the Linux version of it. 2. How many QA people are using the testool? Is there a need to put all the historical resulting log (or part of them) to somewhere public so that other QA can use them as a reference result data (for regression comparison for example)? + Related wiki: http://wiki.documentfoundation.org/QA/Testing/Subsequenttests Thanks Bjoern-michaelsen working on this new stuff in wiki! IMHO, it is expected to investigate the best way to merge it into a common QA/Build process. Any comments on it? -- Yifan Jiang Libreoffice Contact: yifan - irc.freenode.net/libreoffice = http://www.libreoffice.org/ http://www.documentfoundation.org/ ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
[Libreoffice] Libreoffice QA Review and Feedback Gathering - Manual and Localization Testing
[Manual and Localization Testing] + Related wiki: http://wiki.documentfoundation.org/QA/Testing/Manual_Tests The manual testing page looks a bit like a test case execution record. I am not sure if this is good to record all the testing in a single page. Meanwhile cases were already created and were being run in a *testing* Litmus server: https://tcm.documentfoundation.org/ We probably expect to have some solution like that. The benifit of having a general/consistent test case management process/tool is people could do QA work in a quite easy way and avoid overlap working. I can help do documentation stuff and further follow up about this if required. + Related wiki: http://wiki.documentfoundation.org/Language About the localization QA, the wiki page shows 'This process is currently under development'. Would you share your experience on here, so that we can see how could we offer help to do it. -- Yifan Jiang Libreoffice Contact: yifan - irc.freenode.net/libreoffice = http://www.libreoffice.org/ http://www.documentfoundation.org/ ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
[Libreoffice] Libreoffice QA Review and Feedback Gathering - Bug Triage
[Bug Triage]
+ Related wiki: http://wiki.documentfoundation.org/BugTriage
1. The current bug triage process looks working very well. One thing in
lack of fields like:
- 'NEEDINFO'
- 'UNCONFIRMED'
- etc.
Is somebody working on them? And any other field of current bugzilla is
better
off being improved?
2. Multiple language bug reports
I ever saw bugs opened in French, German and Chinese. Some of them were
kept alive when somebody translated while some of them were closed as
invalid since people ignored them.
So do we need an explicit rules for those? After all Libreoffice is being
used by people in the world. We may overlook those real bugs reported by
closing them immediately.
A possible process for such a situation is, instead of setting those bugs
as invalid immediately, to set a timeout threadhold (10 days for
example)to wait a non-English bug translation. After the timeout, we close
the bug as Invalid.
Another solution (great one) might be l10n people add their names to the
http://www.freedesktop.org/wiki/Software/LibreOffice/FindTheExpert
wiki page. Then we could put the names into CC and ask for a translation?
How do you see that?
--
Yifan Jiang
Libreoffice
Contact: yifan - irc.freenode.net/libreoffice
=
http://www.libreoffice.org/
http://www.documentfoundation.org/
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice
[Libreoffice] Libreoffice QA Review and Feedback Gathering - QA People
[QA People] + Related wiki: http://wiki.documentfoundation.org/QA/QA_Team 1. Currently we only have 2 offical QA team volunteers in this page. It is obvious we have more QA people at least from the localization team, and people already doing manual testing and bug triage etc. If you are doing/going to do Libreoffice QA work, and are not included in the list, please put your name and coverage area there. It would be great to have all your people got involved listed! 2. Do we have or plan to have a dedicated QA specific mailing list? If not we may need one. -- Yifan Jiang Libreoffice Contact: yifan - irc.freenode.net/libreoffice = http://www.libreoffice.org/ http://www.documentfoundation.org/ ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
[Libreoffice] Libreoffice QA Review and Feedback Gathering - Title mail
Dear people, The aim of this set of mail threads is to initialize a more detailed discussion of Libreoffice QA. As from reviewing the current status of our wiki page and previous mailing thread, I feel it is quite necessary to have a big map view of current QA status, so that we all have a commen sense of: - who are working on what? - where we are? - what are we going to do next? - what is the most high priority problem of QA work? in a more efficient and cooperated way. Besides I also opened some discussions of current thoughts from my understanding. Would you feel free to add your brilliant ideas, comment, or further questions you want to know, from which I believe most people will also benifit. -- The outline of discussion is divided into 4 sections as coming mails with same Title of this appending different Subtitles: - QA People - Bug Triage - Manual and Localization Testing - Automation Testing Please reply-To-All the corresponding section you are interested in and reply-To-All to this title mail if your comments does not suitable for those sections. -- Finally I will keep working on summarize all of them and to open further discussions on how we are going to the next. Thanks in advance! Best wishes, Yifan -- Yifan Jiang Libreoffice Contact: yifan - irc.freenode.net/libreoffice = http://www.libreoffice.org/ http://www.documentfoundation.org/ ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice] Tools - Media Player
Hi Thomas, On Wed, Feb 23, 2011 at 11:26:55PM +0100, Thomas Arnhold wrote: > Hi Yifan, > > On 02/23/2011 10:47 AM, Yifan Jiang wrote: > > I guess end-users could still bring the menu item back using the menu > > customization UI (Tools->Customize...->Menus). Is that right? > > That's possible. But for writer and calc the background calls are gone. > So it won't work. There's another entry button of the media play in the customized toolbar set. So I think this would also not work based on the context? > Maybe I re-enable them, so someone could still > customize his menus with Media Player enabled. This would be perfectly acceptable in my personal opinion. We don't actually know who will use the stand-alone player in other apps rather than impress, I mean it depends on the end users' personal favour and habits. So IMHO, we should be cautious to *totally* take out an existing feature. Michael? What about your opinion of this? Best regards, Yifan ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice] Tools - Media Player
Hi Thomas, Thanks for your effort! ;-) I guess end-users could still bring the menu item back using the menu customization UI (Tools->Customize...->Menus). Is that right? Best wishes, Yifan On Wed, Feb 23, 2011 at 09:57:37AM +0100, Thomas Arnhold wrote: > On 02/23/2011 05:46 AM, Jean-Baptiste Faure wrote: > > Perhaps you should ask end-users. Some users are using Draw or Writer as > > a replacement of MS-Publisher. Or Writer to edit their website. Maybe it > > is useful in these cases ? > > Right, the website thing came to my mind later, too. But as I said: I > removed the Media Player only from the menu. You could still add Videos > with Insert -> Movie and Sound. And the Playback Toolbar is also still > there (View -> Toolbars -> Media Playback). > > Should I revert these patches?! > > Thomas > ___ > LibreOffice mailing list > LibreOffice@lists.freedesktop.org > http://lists.freedesktop.org/mailman/listinfo/libreoffice ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice] Test script patch review request (1)
Ah...got more reading. `expand` is smarter than I have thought ( I misunderstood it as only fixed space characters can be provided to replace tabs), so to keep the source file looks the same as it used to be. This should be enough to: $ cat /tmp/tabfile | while read fn ; do expand $fn > /tmp/no_initabfile; mv /tmp/no_initabfile $fn; done Then removing trailing spaces. Is that the correct way? Best regards, Yifan On Wed, Jan 05, 2011 at 02:19:00AM -0700, Tor Lillqvist wrote: > > Would you also like to comment my updated method sent yesterday? Thanks! > > Well, it was not clear to me why you want to expand only initial tabs. > Presumably when somebody uses tab characters in a source file, they intend > them to tab to the next multiple of four columns regardless where on the line > they are? That is how the editor shows the source files to the person editing > it. Or am I missing something? > > --tml > > > ___ > LibreOffice mailing list > LibreOffice@lists.freedesktop.org > http://lists.freedesktop.org/mailman/listinfo/libreoffice ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice] Test script patch review request (1)
On Tue, Jan 04, 2011 at 04:07:57AM -0700, Tor Lillqvist wrote: > I admit that having to have the redirection of input to the while loop at the > end, after the "done", does make it harder to read, especially if the loop is > long. In this case the loop is not long, but still... so yeah, using "cat" > here to pipe the file into the while loop is clearer, even if it introduces > an extra process and pipe. Thanks for clarification, I regarded it as a typo :) Since it is just one time script to get a specific task, I didn't think to much of resource usage... ...so in my update script it still sticks to cat pipe, hope it would not so suck, hehe... Would you also like to comment my updated method sent yesterday? Thanks! Best regards, Yifan ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice] Test script patch review request (1)
Hi Tor, Thanks a lot for reviewing and the comments, I haven't even known the '(un)expand' until you told :) To make it concise, do you think it is enough to replace 'Inital' Tabs with 4 space characters, while change other tabs with 1 space character. In addition the trailing spaces could be removed at the same time as the final step. Here is the method I intend to update the patch, your further comments are appreciated, thank you! step 1. Replace Initial tabs with 4 space characters: $ cat /tmp/tabfile | while read fn ; do expand -i -t 4 $fn > /tmp/no_initabfile; mv /tmp/no_initabfile $fn; done step 2. Replace all tabs in the middle/at the end of code with 1 space character: $ cat /tmp/tabfile | while read fn; do expand -t 1 $fn > /tmp/no_tabfile; mv /tmp/no_tabfile $fn; done step 3. Remove all trailing spaces stepping through inc and bas files: $ find | grep -e bas$ -e inc$ | while read fn; do sed -r 's/ +$//' $fn > /tmp/no_trailingspaces ; mv /tmp/no_trailingspaces $fn; done Best wishes, Yifan On Mon, Jan 03, 2011 at 04:51:28AM -0700, Tor Lillqvist wrote: > > cat /tmp/tabfile | sed 's/ //' > /tmp/notabfile; > > Sorry, but just replacing every TAB character with a fixed number (in this > case, four) of SPACE characters is incorrect. To properly expand TAB > characters, each TAB needs to be replaced with a variable number of SPACE > characters, depending on which column the TAB is in. > > For instance if you have a line: > > foo bar > > (i.e. "foo", a TAB, and "bar"), the TAB should be replaced with just one > SPACE. (Assuming the intended tab width is four columns, as it is in OOo/LO. > Note that traditionally the tab width is eight columns.) > > (Also, you would want to use the "g" modifier in the sed 's' command to > replace every TAB on each line, not just the first.) > > Anyway, the "expand" command is the right tool to expand tabs. > > P.S. Your script can be written much simpler, no need to use "cat" so much: > > while read fn sed 's/ //g' < $fn > /tmp/notabfile > mv /tmp/notabfile $fn > done > > (Here still incorrectly using "sed" and not "expand".) > > --tml > ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice] Test script patch review request (1)
I am sorry to bother you to look at this. I am not sure how come the initial dot character was 'eaten', try to re-attached it. /chart2/optional/ch2_lvl1_wizard.bas /chart2/optional/includes/ch2_lvl1a.inc /chart2/optional/includes/wizard/ch2_lvl1_wizard.inc /chart2/optional/includes/wizard/ch2_lvl1_wizard2.inc /chart2/required/includes/ch2_file.inc /chart2/required/includes/ch2_format.inc /chart2/required/includes/ch2_insert_ctl.inc /chart2/required/includes/ch2_toolbars.inc /chart2/tools/ch_tools_chart_type.inc /chart2/tools/ch_tools_select.inc /chart2/tools/ch_tools_statistics.inc /dbaccess/optional/includes/ctrl_Clipboard.inc /dbaccess/optional/includes/ctrl_General.inc /dbaccess/optional/includes/ctrl_Grid.inc /dbaccess/optional/includes/ctrl_PropertyBrowser.inc /dbaccess/optional/includes/ctrl_Several1.inc /dbaccess/optional/includes/ctrl_Several2.inc /dbaccess/optional/includes/ctrl_Spreadsheet.inc /dbaccess/optional/includes/ctrl_TextControl.inc /dbaccess/optional/includes/ctrl_Wizards.inc /dbaccess/optional/includes/db_ADOAccess.inc /dbaccess/optional/includes/db_Dbase.inc /dbaccess/optional/includes/db_hsqldb.inc /dbaccess/optional/includes/db_IndexDesign.inc /dbaccess/optional/includes/db_JDBCMySQL.inc /dbaccess/optional/includes/db_ODBCMySQL.inc /dbaccess/optional/includes/db_Query.inc /dbaccess/optional/includes/db_Relations.inc /dbaccess/optional/includes/db_Spreadsheet.inc /dbaccess/optional/includes/db_Text.inc /dbaccess/optional/includes/frm_FormFilter.inc /dbaccess/optional/includes/frm_Forms.inc /dbaccess/optional/includes/misc_RegisterDatabase.inc /dbaccess/optional/includes/rpt_DateTime.inc /dbaccess/optional/includes/rpt_ExecuteReport.inc /dbaccess/optional/includes/rpt_Formating.inc /dbaccess/optional/includes/rpt_Grouping.inc /dbaccess/optional/includes/rpt_PageNumber.inc /dbaccess/optional/includes/wiz_CopyTableWizard.inc /dbaccess/optional/includes/wiz_DatabaseWizard.inc /dbaccess/optional/includes/wiz_FormWizard.inc /dbaccess/optional/includes/wiz_QueryWizard.inc /dbaccess/optional/includes/wiz_ReportWizard.inc /dbaccess/optional/includes/wiz_TableWizard.inc /dbaccess/optional/includes/xf_Submission.inc /dbaccess/optional/dba_ctrl_Clipboard.bas /dbaccess/optional/dba_ctrl_General.bas /dbaccess/optional/dba_ctrl_Grid.bas /dbaccess/optional/dba_ctrl_PropertyBrowser.bas /dbaccess/optional/dba_ctrl_Several.bas /dbaccess/optional/dba_ctrl_Spreadsheet.bas /dbaccess/optional/dba_ctrl_TextControl.bas /dbaccess/optional/dba_ctrl_Wizards.bas /dbaccess/optional/dba_db_dBase_functions.bas /dbaccess/optional/dba_db_Text.bas /dbaccess/optional/dba_frm_FormFilter.bas /dbaccess/optional/dba_wiz_CopyTableWizard.bas /dbaccess/optional/dba_wiz_FormWizard.bas /dbaccess/optional/dba_wiz_QueryWizard.bas /dbaccess/optional/dba_wiz_ReportWizard.bas /dbaccess/required/includes/MainApp.inc /dbaccess/required/includes/Query.inc /dbaccess/required/includes/ReportBuilder01.inc /dbaccess/required/includes/Xforms01.inc /dbaccess/tools/controltools.inc /dbaccess/tools/dbcreatetools.inc /dbaccess/tools/dbtools.inc /dbaccess/tools/formtools.inc /dbaccess/tools/querytools.inc /dbaccess/tools/reporttools.inc /dbaccess/tools/tabletools.inc /extensions/optional/includes/extensions.inc /extensions/optional/includes/help.inc /framework/optional/f_CJK_GridLayout.bas /framework/optional/includes/basic_dialog_i18n_defaults.inc /framework/optional/includes/basic_eventbinding.inc /framework/optional/includes/basic_usertemplate.inc /framework/optional/includes/basic_vba-compat_import_disabled.inc /framework/optional/includes/options_loadsave_general.inc /framework/optional/includes/options_ooo_paths.inc /framework/optional/includes/configuration.inc /framework/optional/includes/extras_file_open.inc /framework/optional/includes/filedlg_document_properties.inc /framework/optional/includes/filedlg_multiselection.inc /framework/optional/includes/filedlg_passwords.inc /framework/optional/includes/scripting_organizers.inc /framework/optional/includes/security_evilmacro1.inc /framework/optional/includes/security_evilmacro2.inc /framework/optional/includes/security_evilmacro3.inc /framework/optional/includes/security_recommend_password.inc /framework/optional/includes/toolbar_behavior.inc /framework/optional/includes/help_bookmarks.inc /framework/optional/includes/ole_3.inc /framework/required/f_tools_customize.bas /framework/required/includes/help_browser.inc /framework/required/includes/tools_customize.inc /framework/required/includes/wizard_firsttime.inc /framework/required/includes/wizard_mailmerge.inc /framework/required/includes/wizard_webpage.inc /framework/tools/includes/fileoperations.inc /framework/tools/includes/i18n_tools.inc /framework/tools/includes/wizards.inc /global/required/includes/g_customize.inc /global/required/includes/g_option.inc /global/system/includes/iniinfo.inc /global/system/includes/status.inc /global/tools/compressstatus.bas /global/tools/includes/optional/t_basic_ide_tools.inc /global/tools/includes/o
Re: [Libreoffice] Test script patch review request (1)
Forgot to attach :) > where the tabs.auto.filelst.txt is the file list containing tabs. I also > have this file attached. /chart2/optional/ch2_lvl1_wizard.bas /chart2/optional/includes/ch2_lvl1a.inc /chart2/optional/includes/wizard/ch2_lvl1_wizard.inc /chart2/optional/includes/wizard/ch2_lvl1_wizard2.inc /chart2/required/includes/ch2_file.inc /chart2/required/includes/ch2_format.inc /chart2/required/includes/ch2_insert_ctl.inc /chart2/required/includes/ch2_toolbars.inc /chart2/tools/ch_tools_chart_type.inc /chart2/tools/ch_tools_select.inc /chart2/tools/ch_tools_statistics.inc /dbaccess/optional/includes/ctrl_Clipboard.inc /dbaccess/optional/includes/ctrl_General.inc /dbaccess/optional/includes/ctrl_Grid.inc /dbaccess/optional/includes/ctrl_PropertyBrowser.inc /dbaccess/optional/includes/ctrl_Several1.inc /dbaccess/optional/includes/ctrl_Several2.inc /dbaccess/optional/includes/ctrl_Spreadsheet.inc /dbaccess/optional/includes/ctrl_TextControl.inc /dbaccess/optional/includes/ctrl_Wizards.inc /dbaccess/optional/includes/db_ADOAccess.inc /dbaccess/optional/includes/db_Dbase.inc /dbaccess/optional/includes/db_hsqldb.inc /dbaccess/optional/includes/db_IndexDesign.inc /dbaccess/optional/includes/db_JDBCMySQL.inc /dbaccess/optional/includes/db_ODBCMySQL.inc /dbaccess/optional/includes/db_Query.inc /dbaccess/optional/includes/db_Relations.inc /dbaccess/optional/includes/db_Spreadsheet.inc /dbaccess/optional/includes/db_Text.inc /dbaccess/optional/includes/frm_FormFilter.inc /dbaccess/optional/includes/frm_Forms.inc /dbaccess/optional/includes/misc_RegisterDatabase.inc /dbaccess/optional/includes/rpt_DateTime.inc /dbaccess/optional/includes/rpt_ExecuteReport.inc /dbaccess/optional/includes/rpt_Formating.inc /dbaccess/optional/includes/rpt_Grouping.inc /dbaccess/optional/includes/rpt_PageNumber.inc /dbaccess/optional/includes/wiz_CopyTableWizard.inc /dbaccess/optional/includes/wiz_DatabaseWizard.inc /dbaccess/optional/includes/wiz_FormWizard.inc /dbaccess/optional/includes/wiz_QueryWizard.inc /dbaccess/optional/includes/wiz_ReportWizard.inc /dbaccess/optional/includes/wiz_TableWizard.inc /dbaccess/optional/includes/xf_Submission.inc /dbaccess/optional/dba_ctrl_Clipboard.bas /dbaccess/optional/dba_ctrl_General.bas /dbaccess/optional/dba_ctrl_Grid.bas /dbaccess/optional/dba_ctrl_PropertyBrowser.bas /dbaccess/optional/dba_ctrl_Several.bas /dbaccess/optional/dba_ctrl_Spreadsheet.bas /dbaccess/optional/dba_ctrl_TextControl.bas /dbaccess/optional/dba_ctrl_Wizards.bas /dbaccess/optional/dba_db_dBase_functions.bas /dbaccess/optional/dba_db_Text.bas /dbaccess/optional/dba_frm_FormFilter.bas /dbaccess/optional/dba_wiz_CopyTableWizard.bas /dbaccess/optional/dba_wiz_FormWizard.bas /dbaccess/optional/dba_wiz_QueryWizard.bas /dbaccess/optional/dba_wiz_ReportWizard.bas /dbaccess/required/includes/MainApp.inc /dbaccess/required/includes/Query.inc /dbaccess/required/includes/ReportBuilder01.inc /dbaccess/required/includes/Xforms01.inc /dbaccess/tools/controltools.inc /dbaccess/tools/dbcreatetools.inc /dbaccess/tools/dbtools.inc /dbaccess/tools/formtools.inc /dbaccess/tools/querytools.inc /dbaccess/tools/reporttools.inc /dbaccess/tools/tabletools.inc /extensions/optional/includes/extensions.inc /extensions/optional/includes/help.inc /framework/optional/f_CJK_GridLayout.bas /framework/optional/includes/basic_dialog_i18n_defaults.inc /framework/optional/includes/basic_eventbinding.inc /framework/optional/includes/basic_usertemplate.inc /framework/optional/includes/basic_vba-compat_import_disabled.inc /framework/optional/includes/options_loadsave_general.inc /framework/optional/includes/options_ooo_paths.inc /framework/optional/includes/configuration.inc /framework/optional/includes/extras_file_open.inc /framework/optional/includes/filedlg_document_properties.inc /framework/optional/includes/filedlg_multiselection.inc /framework/optional/includes/filedlg_passwords.inc /framework/optional/includes/scripting_organizers.inc /framework/optional/includes/security_evilmacro1.inc /framework/optional/includes/security_evilmacro2.inc /framework/optional/includes/security_evilmacro3.inc /framework/optional/includes/security_recommend_password.inc /framework/optional/includes/toolbar_behavior.inc /framework/optional/includes/help_bookmarks.inc /framework/optional/includes/ole_3.inc /framework/required/f_tools_customize.bas /framework/required/includes/help_browser.inc /framework/required/includes/tools_customize.inc /framework/required/includes/wizard_firsttime.inc /framework/required/includes/wizard_mailmerge.inc /framework/required/includes/wizard_webpage.inc /framework/tools/includes/fileoperations.inc /framework/tools/includes/i18n_tools.inc /framework/tools/includes/wizards.inc /global/required/includes/g_customize.inc /global/required/includes/g_option.inc /global/system/includes/iniinfo.inc /global/system/includes/status.inc /global/tools/compressstatus.bas /global/tools/includes/optional/t_basic_ide_tools.inc /global/tools/include
[Libreoffice] Test script patch review request(0)
Dear people, I've updated several test scripts and intended to make them more reliable. I have tested them in SUSE Linux. Could you help review the patches and if possible help run relevant cases in various platforms. Thank you all for concerning and help! The belowing is the outline and details in the patch * 0001-use-uno-to-invoke-File-Digital-Signature-dialog.patch Old method to callout the dialog by count menu item number. This is always failed here with Gdoc extension installed, which adds a menu item. * 0003-more-stable-export-graphic-test.patch do not verify exported SVG content, instead just verify the exported file is existed. Because the difference against OO.o is, SVG will be rendered by Libreoffice Draw directly instead of imported as ASCII with Writer (which was used by the old script to verify the content). So at this point we lose some verification points which were used in old script, which got the svg content verification involveds. Is it really necessary? If necessary, do you have some ideas to verify this without using Writer to open the SVG? Also the patch replace an inexisted testing picture to an existed one * 0004-use-uno-slot-to-click-File-Save-as-in-Base.patch Reason is the same as 0001. * 0005-slideshow-test-case-update.patch 1. give a more safe coordination for drawing rectangle in the slide page otherwise the testtool may accidently 'click insert chart icon in the slide page' when trying to 'drawing a rectangle' 2. use uno slot to call Slide Show -> Custom Slide Show. just because I think it should be better :) Best wishes, Yifan >From e4a82c917aa75467b671b43b6ff916a39c55af79 Mon Sep 17 00:00:00 2001 From: Yifan J Date: Mon, 20 Dec 2010 13:37:10 +0800 Subject: [PATCH 1/5] use uno to invoke File->Digital Signature dialog. influenced case: f_security_dialogs.bas f_security_certified_docs.bas --- testautomation/global/sid/e_all.sid|1 + .../tools/includes/optional/t_security_tools.inc | 13 ++--- 2 files changed, 3 insertions(+), 11 deletions(-) diff --git a/testautomation/global/sid/e_all.sid b/testautomation/global/sid/e_all.sid index 4c7800b..1a8a0b7 100644 --- a/testautomation/global/sid/e_all.sid +++ b/testautomation/global/sid/e_all.sid @@ -35,6 +35,7 @@ FileSendDocumentAsPDF SID_MAIL_SENDDOCASPDF FileVersions SID_VERSION FileReload SID_RELOAD SID_LASTVERSIONDOC FileProperties SID_DOCINFO +FileDigitalSignatures .uno:Signature FileTemplatesOrganize SID_ORGANIZER FileTemplatesSave SID_DOCTEMPLATE FileTemplatesEdit SID_OPENTEMPLATE diff --git a/testautomation/global/tools/includes/optional/t_security_tools.inc b/testautomation/global/tools/includes/optional/t_security_tools.inc index 28625be..6952f7e 100755 --- a/testautomation/global/tools/includes/optional/t_security_tools.inc +++ b/testautomation/global/tools/includes/optional/t_security_tools.inc @@ -144,17 +144,8 @@ function hOpenDigitalSignaturesDialog() as boolean '///+Open the file-menu call hUseMenu() call hMenuSelectNr( FILE_MENU_POSITION ) - -'///+Select "Digital signatures..." -try -if ( gApplication = "MATH" ) then -call hMenuSelectNr( SIGNATURES_MENU_POSITION_MATH ) -else -call hMenuSelectNr( SIGNATURES_MENU_POSITION_OTHER ) -endif -catch -warnlog( CFN & "Failed to execute menuitem " ) -endcatch + +FileDigitalSignatures ' At this stage either the digital signatures dialog or the messagebox ' is open. In the latter case the function -- 1.7.3.1 >From a3ceca8961e973c99a4d8fe68aec2913655350f2 Mon Sep 17 00:00:00 2001 From: Yifan J Date: Fri, 24 Dec 2010 15:33:22 +0800 Subject: [PATCH 3/5] more stable export graphic test. influenced cases: /testautomation/graphics/optional/d_export_graphic_a.bas /testautomation/graphics/optional/d_export_graphic_b.bas 1. do not verify exported SVG xml content, just verify the exported file is existed. Because SVG will be rendered by Draw directly instead of ASCII import mode (which was used by the old script to verify the content). 2. replace an inexisted testing picture to an existed one --- .../optional/includes/global/export_graphic_2.inc | 32 .../optional/includes/impress/i_slideshow2.inc |4 +- 2 files changed, 2 insertions(+), 34 deletions(-) diff --git a/testautomation/graphics/optional/includes/global/export_graphic_2.inc b/testautomation/graphics/optional/includes/global/export_graphic_2.inc index 5e0a2f3..be5ed49 100644 --- a/testautomation/graphics/optional/includes/global/export_graphic_2.inc +++ b/testautomation/graphics/optional/includes/global/export_graphic_2.inc @@ -613,38 +613,6 @@ testcase tSVG '\ if ( dir(OutputGrafikTBO+sExt) <> "") then Printlog "Ok :-) Saved as:
Re: [Libreoffice] The download link still shows Beta?
Thorsten, Thanks! I am sorry didn't aware there is a WWW component option, and overlooked the existing bug by searching with words in title :( Best wishes, Yifan On Thu, Dec 16, 2010 at 06:12:58PM +0100, Thorsten Behrens wrote: > Yi Fan Jiang wrote: > > The links here looks a bit strange with 'Beta' while we have been in RC > > phase for some while: > > > > http://www.documentfoundation.org/download/ > > > > The word seems embedded in the picture...(from css) > > > Hi Yifan, > > yep, good catch, this was reported as > https://bugs.freedesktop.org/show_bug.cgi?id=32142 > > (I personally think it would be nice to change, but not an absolute > necessity, as long as we're in rc phase). > ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice] The download link still shows Beta?
Wow, thanks David, those look pretty ;-) Yifan On Fri, Dec 17, 2010 at 12:56:29AM +0800, David Nelson wrote: > Hi Yi Fan Jiang, :-) > > On Fri, Dec 17, 2010 at 00:37, Yi Fan Jiang wrote: > > To whom may concern, > > > > The links here looks a bit strange with 'Beta' while we have been in RC > > phase for some while: > > > > http://www.documentfoundation.org/download/ > > The content on those pages is out of date. We're nearly finished > preparing the new LibreOffice site now. You can view it at > http://test.libreoffice.org, and the downloads page there is up to > date. The documentfoundation page will need to be updated. > > David Nelson ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
[Libreoffice] Tools->Options [UI] bugs need love.
Dear people, The 2 bugs reveals some visual flaw in Tools->Options dialog. They look annoying for our brand new release, not sure who's interested taking them? >From my reproducing, this is a general platform problem: Bug 31944 - VBA Properties not fully displayed https://bugs.freedesktop.org/show_bug.cgi?id=31944 >From my preproducing, I only see this in KDE: Bug 31694 - [UI]: Overlapping Items in General Options menu on beta 3 https://bugs.freedesktop.org/show_bug.cgi?id=31694 Best wishes, Yifan ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
