Tommy wrote
Retiered some time ago [can't find thread]. Very sad
Ok, I was afraid that he left the project...
anyway he did a very good job here and everybody will welcome him if he
comes back.
He did:
jmadero wrote
One of the main issues is that FDO doesn't allow you to go from RESOLVED
- WORKSFORME back to UNCONFIRMED.
Hi!
Not true. RESOLVED WORKSFORMEUNCONFIRMED transition is possible with
current fdo status workflow. Just checked that moment ago myself. See this
bug activity:
jmadero wrote
If you mark a bug as WFM, you are unable to go directly back to
UNCONFIRMED - which for me
is strange, I understand if it's marked as FIXED but WFM shouldn't block
you from doing UNCONFIRMED again.
Hi!
Are you sure about that? See this bug activity table:
Stefan Knorr (Astron)-2 wrote
here's a link to an HTML mockup:
http://dl.dropbox.com/u/87946285/libreoffice/feedback/feedback-page.html
Hi!
Did you think about setting up LibreOffice Feedback page using Mozilla
software? It's code is available at github:
Sophie Gautier wrote
I would propose to use QA Contact field for this purpose, at least when
in
the processing (translation, gathering more details) phase.
If it could be the qa@fr list, then it's ok.
Hi!
This have to be Bugzilla registered account. If there is one for qa@fr, then
it could
Sophie Gautier wrote
I've discussed the process with our FR team and they are ok to handle it.
Hi!
Great to hear that! All we need now is a list of people, by language, who
can be cc'ed to work on the bug
when it has non English summary and seems to be a valid report at first
sight.
Sophie
Hi!
Recently I stumbled upon two open source projects (sources are available on
github) to get more volunteers by their interests:
- in bugs department - see http://www.joshmatthews.net/bugsahoy/
- in the development area - see http://whatcanidoformozilla.org/
Those are very simple sites, where
Thorsten Behrens wrote
Hi there,
seen this today -
http://nagappanal.blogspot.de/2012/10/ann-automated-testing-on-mac-atomac-101.html
Did anyone have experience (positive negative) with that tool?
Cheers,
-- Thorsten
Hi.
See
Michael Meeks-2 wrote
There is one already - Bugzilla. I think devs should be teached how to
use
Bugzilla more.
:-) Sure - but a developer's daily interaction involves using many bug
trackers - from LibreOffice, to SUSE, RedHat, Deb-bugs, Apache Issues,
etc. having a single page
Hi.
tl;dr, but IMHO ideal localized MozTrap system could be designed this way:
Tests should be written using some kind of special text editor with
autocomplete, in generic language (or based on English) using UI strings and
then those strings substituted to the language of choice (not only
Michael Meeks-2 wrote
Of course the filters are tested; there were -zero- unit tests for the
RTF filter before we started, it is now perhaps -the- most unit tested
filter that there is - every bug fix Miklos makes has a nice unit test:
better - since the code is shared, that is unit
Michael Meeks-2 wrote
The reason I graph regressions each week is to try to add focus there;
if you can think of another more encouraging way - that'd be
appreciated.
Hi.
Unfortunately those graphs are discouraging in many ways. Especially if one
thinks about upgrading LO...
Michael
Michael Meeks-2 wrote
So - I like the idea of highlighting a small set of the most critical
bugs each-week - say five; and having them linked in the ESC minutes
with a small write-up. Of course that would need to be generated by QA.
The bit that is unworkable in the above is the
Jochen wrote
We need a strategy with a positive, encouraging motto for the developers.
Hi.
Strategy is simple - the time has come to manage bugs better. I could be
mistaken, it is still difficult to me to gather informations from all LO
resources, but I think that today some QA people are
Jochen wrote
IMHO has bfo some right. But:
1) bankruptcy of this system is a little bit exaggerated.
Hi!
Not at all. After reviewing 400 bugs (and counting) I could double 3.5MAB
numbers in an instant.
The main problem is that MAB is a battlefield for users without QA control
and devs IMHO
Rainer Bielefeld-2 wrote
For some of these bugs simply the Bug description still is not
satisfying so that I can understand developers that they pick bugs where
they can start fixing with out much additional preliminary research.
Hi!
Sometimes I am not even sure that devs use Bugzilla
Bjoern Michaelsen wrote
I dont think discussing this on a mailing list will help us find the
silver
bullet to the problems you describe. However, you are most invited to just
us
on the next QA Call on August, 23rd 2012 1400UTC, discussing these topics
on
the phone is usually a lot more
Timur_LOL wrote
It is clear that at the beginning bugs list should contain only bugs
which are *new* in LibreOffice 3.6, but at some time, while some fixes
from MAB 3.5 are integrated in the code, there is a decision on what
to do with the remaining unfixed bugs from a branch (3.5).
Hi.
Michael Meeks-2 wrote
* QA update (Rainer)
+ new bug report page - with search for duplicates thanks to Tollef
Hi.
Nice that Potential Duplicates has been enabled, the same for usernames
autocomplete. Whining could be enabled also. Maybe bugs.freedesktop.org
administrators are going
Florian Reisinger wrote
Somehow it seems to me that Bugzilla is down (With some circumstances
only...) http://www.webpagescreenshot.info/img/862641-81201261840PM
Hi.
Seems it is updated to 4.0.7 now and blazing fast atm...
Best regards.
--
View this message in context:
julien2412 wrote
There's a tracker about coverage, see
https://bugs.freedesktop.org/show_bug.cgi?id=38840
For the moment, no one seemed to be on it (perhaps I'm wrong).
Hi.
What a discovery! I have found some scripts already in the codebase
.
__
If you reply to this email, your message will be added to the discussion below:
http://nabble.documentfoundation.org/Interoperability-of-LibreOffice-and-Microsoft-Office-2013-tp3996056.html
This email was sent by bfo (via Nabble)
To receive all replies by email, subscribe
:
http://nabble.documentfoundation.org/LibreOffice-code-coverage-tp3994901.html
This email was sent by bfo (via Nabble)
To receive all replies by email, subscribe to this discussion:
http://nabble.documentfoundation.org/template/NamlServlet.jtp?macro=subscribe_by_codenode=3994901code
Hi.
In regards to https://bugs.freedesktop.org/show_bug.cgi?id=51352#c3
I think that imported bugs which are in RESOLVED FIXED state should get some
kind of notification by a triagger.
LO devs, with the current backlog, should not waste time for bugs, which
are already fixed in the other codebase.
Michael Stahl-2 wrote
Linux version is LDTP, Windows version is Cobra and Mac version is PyATOM
(Work in progress).
can all of these execute the same tests?
surely writing tests 3 times is not the way to go.
With LDTP and WinLDTP, the script API part will be the same. The only
places
Hi.
I stumbled upon Cobra – WinLDTP, Windows version of Linux Desktop Testing
Project open sourced by VMWare
recently. Using this tool, the GUI functionality of an application can be
tested in Windows XP SP3, Windows 7 SP1, Windows 8 development release.
Libre/OpenOffice is mentioned. Did
Bjoern Michaelsen wrote
Crash counter (search for libreoffice-core):
https://errors.ubuntu.com/
Open LibreOffice crasher bugs by most affected users:
Open LibreOffice crasher bugs by bug heat:
This s very cool. Question - why I have mostly page not find errors when I
click in the Bugs
27 matches
Mail list logo
