Hi all,
in my opinion it would be great to have a component for accessibility; it could
let developers to better focus on accessibility bugs and, on the other hand,
blind people to know that accessibility is important for this project and that
submitting bug reports of this type is more than en
Hi,
for bugreport [1] tester for Base with MS Access 2007/2010 wanted.
Who can help?
[1] https://bugs.freedesktop.org/show_bug.cgi?id=43187
Regards
Jochen
___
List Name: Libreoffice-qa mailing list
Mail address: [email protected]
C
Hi,
for bugreport [1] tester for Base with MS Access 2007/2010 wanted.
Who can help?
[1] https://bugs.freedesktop.org/show_bug.cgi?id=43187
Regards
Jochen
___
List Name: Libreoffice-qa mailing list
Mail address: [email protected]
C
Hi,
for bugreport [1] tester for Base with MSAccess 2007/2010 wanted.
Who can help?
[1] https://bugs.freedesktop.org/show_bug.cgi?id=43187
Regards
Jochen
___
List Name: Libreoffice-qa mailing list
Mail address: [email protected]
Ch
Dear Community,
The Document Foundation is happy to announce the second release
candidate of LibreOffice 3.6.1. The upcoming 3.6.1 will be the first
in a series of frequent bugfix releases, for our feature-packed 3.6
branch. Please be aware that LibreOffice 3.6.1 RC2 is not ready for
production us
On 08/25/2012 02:30 AM, Rainer Bielefeld wrote:
Joel Madero schrieb:
when we actually put a bug into NEEDINFO status we put a comment that
has a small blurb on our procedure. Something like "we have put this bug
in NEEDINFO status because we need you to provide.we will leave the
bug in this
On 08/25/2012 04:46 AM, Rainer Bielefeld wrote:
Joel Madero schrieb:
This is only in the first phase but I'm aiming to make the triage page
more complete, easy to read, and have all the information (at least
linked) to effectively triage. Here is the link, feel free to comment,
check it out ever
Hi Bjoern,
Am 25.08.2012 14:21, schrieb Bjoern Michaelsen:
However, while 10 days is usually enough, I would extend
to maybe 30 days to allow for things like "reporter on vacation" etc.
Counterargument: reporter receives a mail. If the bugreport is important
to the reporter he will answer th
Hi,
On Sat, Aug 25, 2012 at 11:30:16AM +0200, Rainer Bielefeld wrote:
> that's to long. Be sure, the info provider will answer within a week
> or never. So it's common sense that a bug can be closed after 10-14
> days if there is no answer and if it can be expected that it will
> not be possible t
Hi Florian,
Am 25.08.2012 13:15, schrieb Florian Reisinger:
Am 25.08.2012 um 10:56 schrieb Jochen :
IMHO in Bugzilla exits more status-types:
ASSIGNED
PLEASETEST
Not available right know with product= Libreoffice
REOPENED
VERIFIED
What do you mean with "Not available"?
IMHO is your statemen
Joel Madero schrieb:
This is only in the first phase but I'm aiming to make the triage page
more complete, easy to read, and have all the information (at least
linked) to effectively triage. Here is the link, feel free to comment,
check it out every once in awhile as I'm trying to do updates some
__
Florian Reisinger
Von meinem iPad gesendet
Sent via iPad
Am 25.08.2012 um 10:56 schrieb Jochen :
> Hi Joel,
>
> Am 25.08.2012 00:34, schrieb Joel Madero:
>> This is only in the first phase but I'm aiming to make the triage page
>> more complete, easy to read, and have all the information (at
Hi *,
Am 25.08.2012 11:30, schrieb Rainer Bielefeld:
Joel Madero schrieb:
we will leave the bug in this status for 6 months
that's to long.
+ 1
I close those bugs INVALID if there was no reply.
+ 1
But sometimes there is additional discussion, users try to reproduce and
so on and
Joel Madero schrieb:
when we actually put a bug into NEEDINFO status we put a comment that
has a small blurb on our procedure. Something like "we have put this bug
in NEEDINFO status because we need you to provide.we will leave the
bug in this status for 6 months
Hi,
that's to long. Be
Hi Joel,
Am 25.08.2012 00:34, schrieb Joel Madero:
This is only in the first phase but I'm aiming to make the triage page
more complete, easy to read, and have all the information (at least
linked) to effectively triage. Here is the link, feel free to comment,
check it out every once in awhile a
Roman Eisele schrieb:
IMHO my little error indicates that, sooner or later, we need to open a
new "LibreOffice 3.7 most annoying bugs" bug list ;-).
Hi,
this MAB proceeding is approved, and I believe we should no longer
hesitate to create a a Task Bug for this. The only thing I would do
dif
Hello all,
today I added a bug from the current master build to our "LibreOffice
3.6 most annoying bugs" list (bug 6) -- only to realize a few
minutes later that now, because 3.6 is released, the master is
3.7alpha0, and therefore bugs from the master builds should _not_ be
added anymore
17 matches
Mail list logo