Re: [Libreoffice-qa] REMINDER: Release 4.0.1.2 from libreoffice-4-0-1 branch

2013-02-22 Thread Petr Mladek
Hi Dan,

first thanks a lot for testing LibreOffice release candidates. It is
important job.

Dan Lewis píše v Čt 21. 02. 2013 v 09:39 -0500:
 On 02/21/2013 09:16 AM, Petr Mladek wrote:
  IMPORTANT: There are not two weeks between rc1 and rc2 this time. It is
  another side effect of the late schedule change when we used two weeks
  between 4.0.0 betas and RCs. We were not able to shift the feature
  freeze and final release.
 
  This should be the last anomality. There should be always two weeks
  between all betas and rcs from now on,
  see https://wiki.documentfoundation.org/ReleasePlan.
 
 
  Best Regards,
  Petr
   I read your first link, and the summary on that page is not 
 psychologically sound. Study after study has shown that when people work 
 on a deadline, they begin to work faster as they approach the deadline. 
 (Staying up all night in college when a paper is due the next morning is 
 one common example.)
   Now we do not have the time between RC1 and RC2 to properly test 
 the latter for potential bugs. So, is it possible that we will have to 
 fix some bugs for 4.0.2 because we did not have the time to test and 
 find it in 4.0.1 RC1 or RC2?

I am a bit confused. :-) In the first paragraph you suggest that most of
the work is done the last night before the deadline. In the second
paragraph, you suggest that one week is not enough. So, what change do
you actually suggest?

   Will this be the last anomaly? I doubt that very much. Any time 
 there are as many changes in LibreOffice between major versions, you are 
 likely to have anomaly as we just did.

Yes, there might be another anomality if we change the schedule again.
Though, this is the last anomality caused by the last schedule rework.
If I did not make a mistake, all the further 4.0.X, 4.1, 4.2 release
have two weeks between betas and RCs.

   Beside, it appears that this schedule does not consider how many 
 people are available in QA to test what the developers produce. None of 
 us have unlimited time available for testing. If we are going to have a 
 quality produce, we need the time to thoroughly test the software. 
 Please put that in the schedule too.

This is why we started to use two weeks between between betas and RCs. I
am afraid that we could not do much more if we do not want to lose the
effect of the frequent time based releases.

We are not able to catch all regressions during testing. We could cover
only the most important areas with the current resources. Each
regression or bug is less painful when it can be fixed in the next
bugfix release that is available only few weeks after the previous one.

We currently use the following tricks to reduce potential regressions:

1. All commits for already released product are reviewed by another
developer before pushing. It helps to find potential problems in time.
Another side effect is that it is more expensive, so only important or
trivial fixes pass this process = development in the stable branch is
under control.

2. We create unit tests for many fixed bugs. They are proceed for every
build. So, we are sue that these bugs never appear again in the future.

3. There is the testing done by the QA team. It is important but not
much organized these days. I think that most people just install the
last build and use it for daily tasks, verification of bugs, ... It is
kind of random testing but it covers the basic areas out of box.

IMHO, it would be great to have the result of manual testing a bit more
organizes and documented. Then we could know be sure that something was
really tested. Then we could have better arguments about what time is
really necessary for testing. I am looking forward to have more people
using http://manual-test.libreoffice.org.
See also https://wiki.documentfoundation.org/QA/Testing/Regression_Tests


Regarding 4.0.1 release. It is pity that there is only one weeks between
rcs but there are still two weeks between rc1 and final publishing. All
changes for 4.0.1.2 build need 3 reviewers, so we are very careful what
goes in. There is really minimal chance of regressions between 4.0.1.1
and 4.0.1.2 builds.

I hope that it looks more optimistic now.

Best Regards,
Petr



___
List Name: Libreoffice-qa mailing list
Mail address: Libreoffice-qa@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/

Re: [Libreoffice-qa] minutes of ESC call ...

2013-02-22 Thread Michael Meeks

On Thu, 2013-02-21 at 20:56 +0100, Michael Stahl wrote:
 On 21/02/13 17:00, Michael Meeks wrote:
  + full-word selection / editing ergonomics cf. UX-advise
https://bugs.freedesktop.org/show_bug.cgi?id=46517
  + pending input from Caolan / Cedric / Michael S
 
 so i have finally looked at this bug and added a comment, which
 basically says meh. how the heck did this get on the ESC agenda?

UX team asked for some input there :-)

ATB,

Michael.

-- 
michael.me...@suse.com  , Pseudo Engineer, itinerant idiot

___
List Name: Libreoffice-qa mailing list
Mail address: Libreoffice-qa@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/



Re: [Libreoffice-qa] [libreoffice-users] Re: MySQL-Connector

2013-02-22 Thread Alex Thurgood

Le 22/02/2013 14:02, Dan Lewis a écrit :

Hmm, some strange things going on somewhere :


-rw-rw-r-- 1 1000 1000 5379260 janv.  3 03:44 
/home/alex/Development/libo/core/mysqlc/unxlngx6.pro/bin/mysql-connector-ooo.oxt



-rw-rw-r-- 1 1000 1000 2575973 févr. 13 12:20 
/home/alex/Development/libo/core/solver/unxlngx6.pro/bin/mysql-connector-ooo.oxt



-rw-rw-r-- 1 1000 1000 2575973 févr. 13 12:20 
/home/alex/Development/libo/core/workdir/unxlngx6.pro/ExtensionTarget/mysql-connector-ooo.oxt



I have no idea why the /ExtensionTarget and /solver copies of the OXT 
are only half the size of the unxlngx6.pro/bin copy. Will post on dev list.


Alex

___
List Name: Libreoffice-qa mailing list
Mail address: Libreoffice-qa@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/


Re: [Libreoffice-qa] Looking for PyUno Contributor(s)

2013-02-22 Thread Joel Madero
Several developers have told me that python and uno will be needed to
extract the data from FDO, create a spreadsheet from this data and then
create the graphs/summaries that I am hoping we can create automagically.


If I'm incorrect, please let me know what is correct - but I'm pretty sure
that someone with some PyUno skills will be needed.

Best.
Joel


On Fri, Feb 22, 2013 at 8:03 AM, Stephan Bergmann sberg...@redhat.comwrote:

 On 02/20/2013 04:11 PM, Joel Madero wrote:

 I am one of the members of the Quality Assurance team with LibreOffice
 and we are looking for a volunteer to work with myself designing (and
 coding) the framework to start automating our stats. It's been on my
 list for much too long and I just don't have the technical know how to
 do it. If there are are users or developers who can slowly get this
 accomplished it would greatly help QA as well as Marketing as our stats
 are done almost completely manually at this point, not only is this time
 consuming but it's also likely that there could be mistakes or missing
 data.


 How is the above related to PyUno (i.e., the Python-UNO bridge)?

 Stephan




-- 
*Joel Madero*
LibreOffice QA Volunteer
jmadero@gmail.com
___
List Name: Libreoffice-qa mailing list
Mail address: Libreoffice-qa@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/

[Libreoffice-qa] [ANN] LibreOffice 4.0.1 RC1 available

2013-02-22 Thread Thorsten Behrens
Dear Community,

The Document Foundation is pleased to announce the first release
candidate of our upcoming LibreOffice 4.0.1. This will be the first in
a series of frequent updates to our feature-packed 4.0 branch. Please
be aware that LibreOffice 4.0.1 RC1 is not ready for production use,
you should continue to use LibreOffice 4.0.0 for that.

The release is available for Windows, Linux and Mac OS X from our QA
builds download page at

  http://www.libreoffice.org/download/pre-releases/

Should you find bugs, please report them to the FreeDesktop Bugzilla:

  https://bugs.freedesktop.org

A good way to assess the release candidate quality is to run some
specific manual tests on it, our TCM wiki page has more details:

 
http://wiki.documentfoundation.org/QA/Testing/Regression_Tests#Full_Regression_Test

  - or checkout our manual test database for starting right away -

 http://manual-test.libreoffice.org/runtests/

With this release candidate, the Android Impress Remote should work on
all platforms - if you would like to test, an updated Android package
is available here:

 
http://downloadarchive.documentfoundation.org/libreoffice/old/sdremote-1.0.3/playstore/ImpressRemote.apk
 
 (and note https://wiki.documentfoundation.org/Development/Impress/RemoteHowTo)

For other ways to get involved with this exciting project - you can
e.g. contribute code:

  http://www.libreoffice.org/get-involved/developers/

translate LibreOffice to your language:

  http://wiki.documentfoundation.org/LibreOffice_Localization_Guide

or help with funding our operations:

  http://donate.libreoffice.org/

A list of known issues and fixed bugs with 4.0.1 RC1 is available
from our wiki:

  http://wiki.documentfoundation.org/Releases/4.0.1/RC1

Let us close again with a BIG Thank You! to all of you having
contributed to the LibreOffice project - this release would not have
been possible without your help.

Yours,

The Document Foundation Board of Directors

The Document Foundation, Zimmerstr. 69, 10117 Berlin, Germany
Rechtsfähige Stiftung des bürgerlichen Rechts
Legal details: http://www.documentfoundation.org/imprint


signature.asc
Description: Digital signature
___
List Name: Libreoffice-qa mailing list
Mail address: Libreoffice-qa@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/

Re: [Libreoffice-qa] [libreoffice-users] Re: MySQL-Connector

2013-02-22 Thread Dan Lewis

On 02/22/2013 08:24 AM, Alex Thurgood wrote:

Le 22/02/2013 14:02, Dan Lewis a écrit :

Hi Dan,


  Some very good news!!! ... and some questions.
  Last evening, I deleted the libo folder and basically began again
using git. I let make run overnight. This morning, I accidentally ran
make install getting an error message of not being able to create a
folder in /usr/... . So, I used sudo make install instead. The build
was installed in /usr/lib/... . So, being curious, I tried sudo make



Hmm, you should've probably done a make dev-install instead of make 
install, as now, you've got a link to your dev build in your 
/usr/lib/, i.e. it will have overwritten any default LO installation 
that you already had, I think. The advantage of make dev-install is 
that it keeps everything in your LO development directory.




install instead. The build was installed within the solver folder as it
should be. I made ooenv executable and ran it. Since then I have run
soffice and looked at Help  About LibreOffice. I now have my own alpha
build number!
  One further test: I ran Base in my new LO-DEV opening MySQL.odb
which connects to my MySQL server. (This is a copy of the file I use to
connect to MySQL. So, if it becomes corrupted, I still have the original
database file.) I successfully connected to the MySQL server.
  Again because I was curious, I looked at the libreoffice
configuration folder, specifically the extension folder. It contained
buildid file which contained a number. I checked this number against the
build number of my new Alpha version. They matched.
 It appears that I have created an alpha version of the MySQL native
connector. So where is this connector in the extension folder? What is
the next step to convert it into the .oxt final version?


The connector itself isn't alpha anything, as the actual connector 
libary code doesn't change version much, and was only bumped to 1.0.2 
last year with a change in the requirement for the version of 
libmysqlclient.


As for its whereabouts, you should be able to find it here :

/core/workdir/unxlngx6.pro/ExtensionTarget/mysql-connector-ooo.oxt

and

/core/solver/unxlngx6.pro/bin/mysql-connector-ooo.oxt

and

/core/mysqlc/unxlngx6.pro/bin/mysql-connector-ooo.oxt


In my builds, it has a size of about 2Mb. This is because the 
connector links to libmysqlclient and libmysqlcppconn, whereas on the 
Mac, it is packaged altogether with these libraries (or at least it 
should be) leading to an OXT file that weighs in at about 4Mb.


Alex


 What I have done:
Created a folder for the files for the LO build: LO-Build.
Added the AOO mysql-native-connector 1.0.1 to LO 4.0.0.3, and closed LO.
Installed libmysqlclient18 and libmysqlcppconn5
Used git to download the master build.
Ran autogen.sh --with-ext-mysql-connector --with-system-mysq
Ran make dev-install
Made ooenv executable and ran it.
Ran soffice in the program folder of my new alpha build.
 But when I searched for mysql-connector on the command line (I ran 
sudo updatedb first). I found a folder named 
lu17qwu9.tmp_/mysql-connector-ooo-1.0.1-linux-intel.oxt. This is located at
/home/dan/.config/libreoffice/4/user/uno_packages/cache/uno_packages/. I 
had earlier also installed the same mysql-native-connector on LO 
3.6.5.2. If it matters, doing this search I found a similar folder in 
/home/dan/.config/libreoffice/4/user/uno_packages/cache/uno_packages/:

luxhljqk.tmp_/mysql-connector-ooo-1.0.1-linux-intel.oxt/.
 So, the question is this: Where is the mysql-connector that was 
suppose to be built with LO?


--Dan
___
List Name: Libreoffice-qa mailing list
Mail address: Libreoffice-qa@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/