Re: [Libreoffice-qa] Volunteer for QA talk at FOSDEM needed

2013-01-07 Thread Cor Nouws
Bjoern Michaelsen wrote (07-01-13 19:36) On Mon, Jan 07, 2013 at 07:12:38PM +0100, Markus Mohrhard wrote: the QA talk at FOSDEm still needs a volunteer. It would be great if one of you would be able to give this presentation. It will be on Sunday morning in the Libreoffice dev-room. I really c

Re: [Libreoffice-qa] Volunteer for QA talk at FOSDEM needed

2013-01-07 Thread Bjoern Michaelsen
On Mon, Jan 07, 2013 at 07:12:38PM +0100, Markus Mohrhard wrote: > the QA talk at FOSDEm still needs a volunteer. It would be great if > one of you would be able to give this presentation. It will be on > Sunday morning in the Libreoffice dev-room. I really cant make it to FOSDEM this year, so som

[Libreoffice-qa] Volunteer for QA talk at FOSDEM needed

2013-01-07 Thread Markus Mohrhard
Hey guys, the QA talk at FOSDEm still needs a volunteer. It would be great if one of you would be able to give this presentation. It will be on Sunday morning in the Libreoffice dev-room. Please consult https://wiki.documentfoundation.org/Marketing/Events/Fosdem2013 for more information. The talk

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

2013-01-07 Thread Petr Mladek
On Thu, 2012-12-13 at 17:16 +, Michael Meeks wrote: > * 4.0 pending tasks > + MSI file re-name to be renamed for 4.0 LibreOffice > + also rename the Linux download tar-balls (Fridrich) > + and Mac packages. > + causes some pain for download script

Re: [Libreoffice-qa] Test master or latest branch?

2013-01-07 Thread Rainer Bielefeld
Pedro schrieb: Hi Pedro, I believe currently it is not a big difference whether you test Branch 4.0 or Master 4.1. The very most bugs you find in 4.1 will also be in 4.0, and any fix will be done in Master first. Nevertheless, I recommend to focus un 4.0 branch, especially intensive working

[Libreoffice-qa] Test master or latest branch?

2013-01-07 Thread Pedro
Hi all In theory running the latest master build should be the correct option for someone doing QA. Since fixes are added to master and then "cherry-picked" to the branches any fixes added to master should be included in the branches (or so I understand...) However the updated information in the