Hi!
Still down!
Florian Reisinger (Von meinem iPad gesendet / Sent via iPad)
Am 10.09.2012 um 20:09 schrieb Rainer Bielefeld
:
> Hi,
>
> Bugzilla seems to be down?
>
> CU
>
> Rainer
> ___
> List Name: Libreoffice-qa mailing list
> Mail address: Libr
Yi Fan Jiang schrieb:
Hi Miguel,
It looks great! I think it is valuable to take the test case to our
regression test base Moztrap,
HI,
yes, of course, it's important to increase intensity of pre-release
routine checks.
Best regards
Rainer
___
Hi Miguel,
It looks great! I think it is valuable to take the test case to our regression
test base Moztrap,
so we will at least have the conditional format checked in each major release
testing.
https://wiki.documentfoundation.org/Moztrap
To help other people how to test the document, do y
Hi,
relating with the new design of conditional formatting, in my opinion it is
necessary to check the proper functioning of it, especially to avoid
compatibility problems with versions of LibreOffice not including the new
design (up to 3.5)
After a short exchange of views with Marcus, I have mad
Hi,
Bugzilla seems to be down?
CU
Rainer
___
List Name: Libreoffice-qa mailing list
Mail address: [email protected]
Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa
Problems? http://www.libreoffice.org/g
Weekly update and reminder that we're still looking for people to help out.
Progress is ongoing but it's slowed down a bit. Thanks to everyone
continuing to help. Here is the link to the spreadsheet again:
https://docs.google.com/spreadsheet/ccc?key=0ApS-XtOUGGH5dDIwaXN1YnNsM0h4RXFKdVhvb2RRb0E#gid
On Thu, Sep 06, 2012 at 04:42:11PM +0100, Michael Meeks wrote:
> * QA update (Rainer)
> + HardHacks:
> ID OS Component - Summary
>
> 32948 Linux Libreoffice/Database(?) - Address Book Data S
On Wed, Sep 05, 2012 at 09:24:41PM +0200, Bjoern Michaelsen wrote:
> On Wed, Sep 05, 2012 at 06:30:30PM +0200, Lionel Elie Mamane wrote:
>> So if you go to https://bugs.freedesktop.org/show_bug.cgi?id=37361 (LO
>> 3.5 MAB), you have to click through on *each* resolved bug to read the
>> bug log an
