Joel Madero schrieb:
So I'm trying to streamline
Hi,
looks plausible. Unfortunately the queries for UNCONFIRMED bugs are not
reliable (not because of technical issues, but because info in the
reports often is incorrect), so that the priority often is not clear
until the work has been
Hi,
in discussions I sometimes read statements like „...formal vote next
call”. I think here some clarification is required.
The QA call has no command of the QA community. The calls and their
participants are not a formal entity of TDF. The only legitimation of
the results of these calls
Petr Mladek schrieb:
Please, do not move too much content there unless it will be easy to
update it.
Hi,
yes, such technical details should remain in the Wiki were they can be
adapted easily to latest results.
The Silverstripe version should have focus on nice viewing and inviting,
clear
V Stuart Foote schrieb:
I asked a very specific question that is appropriately
addressed to any active QA participant--is there anyone that is building
master on Windows and not having the problem of fdo#63680?
Hi,
of course that is an appropriate and useful question. That is one of the
Bjoern Michaelsen schrieb:
Hmmm, I kinda feel its not good to put that on a website with restricted access
Hi,
+1
I think we should distinguish 2 different (but overlapping, of course)
areas.
a) What we here are talking about every day! What bugs are blockers, how
to use
Hi all,
I think currently it is rather useless to submit additional bugs
concerning WriterPrinting OLE problems. We already have lots of bugs
similar to Bug 60280 - PRINTING of TABLE borders, borders around
paragraphs and footer, some graphic elements suppressed by OLE objects
in document,
Robinson Tryon schrieb:
Rainer, how does this plan sound to you?
Hi Robinson,
not good! We will not create complicated wrong rules for things what are
easy to understand. And whether a Version still is useful for indicating
where in the history a (newly reported) bug appeared has nothing to
Florian Reisinger schrieb:
I totally agree and closed my bug(s) created today...
Hi,
I would simply call the bug Test Document for Bug xxx and leave it
open related to Bug 60280. And if someone on German mailing list,
ASK-LibO or wherever thinks he has an interesting related sample
Joel Madero schrieb:
This bug has been in NEEDINFO state for more than 180 days
Hi,
this text IMHO is much too elaborated and prim, please do not use it.
If you plan such actions please leave a related description in the Wiki,
most here do not have the time to find all scattered info in
Sophie Gautier schrieb:
please consider that we (FR group) are acting as a community and not as
individuals,
Concerning this process
https://wiki.documentfoundation.org/QA/BSA/Localization
it seems a bit bureaucratic to me.
Hi Sophie,
I agree. Currently I see a tendency that the QA calls
Robinson Tryon schrieb:
Per discussion at the meeting today, we generally agreed to the following:
Hi,
I left some hints and thoughts on
https://wiki.documentfoundation.org/Talk:QA/Meetings/2013/April_19.
CU
Rainer
___
List Name: Libreoffice-qa
Hi all,
today I replaced lots of single E-Mail addresses in the sender
blacklist by smart ReExp filters, what should find also similar
addresses. I hope that will reduce amount of SPAM here, I will continue
that rework soon.
Best regards
Rainer
Adam Fyne schrieb:
What is the difference between bugs posted under 'Writer' section with the
keyword 'FILEOPEN',
Hi Adam,
although the answer might not be really satisfying: Components starting
with a lowercase [1] are for developers wrangling deep in the guts of
LibO, we normal users
Hi all,
today I repaired a broken sender filter (what might have caused some
additional SPAM on this list) and added some additional SPAM filter
rules. Most of them will simply discard the messages, some of them hold
the mails for moderation.
@Florian:
Please tell me if no. of moderation
Marc Paré schrieb:
[...] LibreOfficeBox is not in the list. Should it not be included?
Hi Marc,
I don't think so, for 1 Bug all 3-4 years sub component all other
problems should be sufficient ;-)
So it looks:
https://bugs.freedesktop.org/show_bug.cgi?id=63648
Best regards
Rainer
Hi,
some of our Sub Components have been created to grant easy and
effective queries, but it is rather improbable that someone using the
BSA will need these Sub Component for a bug report. Such Sub components
can be defined on the help pages for the components as I demonstrated
for Tinderbox
Florian Reisinger schrieb:
As this (SI-GUI) is now an official LibreOffice project I lost the
tracker at github
Hi Florian,
thank you for the great tool. I will take your request to the wishlist.
Joel and I stumbled upon several inconsistencies and some incompleteness
in the Bugzilla
Florian Reisinger schrieb:
Hi Florian,
how will distribution be in future? A solution with Extensions website
(what will need the latest build there) or will you remove SI-GUI from
there and only contribute links on the QA Wiki pages and similar?
Best regards
Rainer
Hi Florian
Here a quick solution keeping the current Extensions Component with
correct Bugzilla Syntax you see on
https://wiki.documentfoundation.org/BugReport_Details#Extensions
until we have a final decision. Unfortunately (of course) the SI-GUI
name will break consistence with older
As announced here
http://lists.freedesktop.org/archives/libreoffice-qa/2013-April/004128.html
today I unchecked Bugzilla flag Enabled For Bugs for following versions.
So following versions will be removed from the LibO Versions dropdown
for bug reports and for editing existing bugs. The
Rainer Bielefeld schrieb:
I am thinking about a Version picker cleanup by removing most 3.3.
Versions.
Hi,
unfortunately that only will bring progress for the Bugzilla Version
Dropdowns, but not for the BSA Vrsion selectors before a fix for Bug
55460 - BUGZILLAASSISTANT: Exclude inactive
Pedro wrote:
Does this also mean that 3.4 versions can already be removed from the
bugzilla Version picker? And 3.5 versions after the 18th of this month?
Hi Pedro,
no, we can't. Version info in BZ should show where the bug appeared (or
at least has been observed the first time), also see
Pedro schrieb:
The point here is that if a version is past the EOL and nobody will fix bugs
in that branch, there is no point in reporting bugs first observed in 3.4 or
3.5 (otherwise you should NOT remove 3.3 from the list either)
Hi Pedro,
you are completely wrong, I doubt that you read
Hi,
I am thinking about a Version picker cleanup by removing most 3.3. Versions.
Currently we have 14 different Versions in the picker.
We obviously still need 3.3.0 Beta 2, what is our Version for
inherited Bugs.
Within the last 180 days we had 50 bug reports for the other 3.3.
Versions
Petr Mladek schrieb:
Ah, this sounds pretty bossy.
Hi,
yes, may be. My tone reflects my exception. I see too much unqualified
discussion. Before thinking about changes everybody should have have
understood the current system, why it is how it is? With such a base
improvement seems more
Hi Andreas,
disc...@de.libreoffice.org is already working on the problem
Best regards
Rainer
___
List Name: Libreoffice-qa mailing list
Mail address: Libreoffice-qa@lists.freedesktop.org
Change settings:
Jochen schrieb:
I added links to bugzilla from the German QA-Wiki (see [1]). Is it okay?
Hi Jochen,
I also am not satisfied with the current search by click on the Sub
Component names. But I had no good ideas and to much other todos. So
your query links might be a great service, but
Tollef Fog Heen schrieb:
Seems to be asciibetical, and 4 sorts before M.
Hi Tollef,
yes, that matches with my results. Some inconsistencies with Versions
starting with a non-numeric character we will discuss internally, may be
we rename or live with it or ask you for a trick (no message
Rainer Bielefeld schrieb:
If I do not read concerns
Hi,
no concerns, so done
https://wiki.documentfoundation.org/BugzAssHlp_WWW_long
CU
Rainer
___
List Name: Libreoffice-qa mailing list
Mail address: Libreoffice-qa@lists.freedesktop.org
Change
Hi,
I see that the Change to later Version Warning Enhancement is under
construction - great!
I am planning to remove the Impress remote Versions from Bugzilla within
next hours. I discussed that with Joel and consensus is that
a) currently we do not need that, it's enough to handle that
Today I removed the Impress Remote Versions from Bugzilla.
Proceeding until a final Solution for bug handling with LibO related
tools: Like with Enhancements
https://wiki.documentfoundation.org/BugReport_Details#Version_Picker:_Particular_Versions
CU
Rainer
P.S.: In this thread I want to
Michael Meeks schrieb:
Thanks for the link - make sense to me, though I was confused by the
comment until I read the page.
Hi,
if someone has an idea for a more intuitive wording instead of (See in
Summary) please let me know here in the list, tat can be modified
without causing
Today I added full syntax BSA Help to the Wiki on
https://wiki.documentfoundation.org/BugReport_Details#Android_Impress_Remote.
Works fine from there (for example: selects correct Component Version in
picker), should also work from BSA after an update there and fix the not
working Read more
Tollef Fog Heen schrieb:
It's actually there. Now it even just displays when the list index
increases (that is, we assume the versions are sorted with the lowest on
top). This seems to be true atm, at least.
Hi Tollef,
thank you for feedback. Unfortunately it seems some more sophisticated.
Rainer Bielefeld schrieb:
but currently I can't
remember where. I will do some tests tomorrow.
Hm,
Browser cache or whatever else? Currently I indeed only see that Master
old 3.6 special case where we get a wrong alarm.
CU
Rainer
___
List Name
Nino Novak schrieb:
Am 02.04.2013 11:45, schrieb Bjoern Michaelsen:
I cleaned up:
Hi,
yes, that really looks more pleasing than the boring default Wiki TOC
page header, and it is much more clear, well arranged.
Best regards
Rainer
___
List
Hi Joel,
my experience is that FDO sitewranglers most times simply ignore
Enhancement Requests concerning FDO infrastructure (Bugzilla) if there
is no obvious support by ESC or other TDF well known official members.
So I created my recommendation on
Sophie Gautier schrieb:
Just send the bug id to the qa@fr list any time you find one and we will
deal with it.
Hi,
but that's only possible for subscribers?
Jean Baptiste Faure jbf.fa...@sud-ouest.org told on this list that he
is willing to translate reports in French language, from time
Robinson Tryon schrieb:
Bugzilla is for bugs that we're willing to address/fix as a project,
Hi Robinson,
I am (more or less) the the creator of the LibO Bugzilla bug tracking
system, so I think I have some overview what should be done and what
should not be done.
I'll leave some notes
Today I added myself as Default QA contact to ensure that Authors of
the Extensions will be informed about the bug. Currently the author is
invisible for most users on Extensions Website.
I will check existing Bugs and contact authors where necessary.
I will try to find a solution with
Joel Madero schrieb:
I added the source document to the wiki:
Hi Joel,
the .jpg in the wiki is portrait, your document.draw landscape. I would
prefer portrait, because that would match better with the normal use of
those flowcharts. Is an alternative top-down-workflow portrait version
Hi Sophie,
with the fix for Bug 60958 BUGZILLAASSISTANT: Greeting text should tell
that goal is to make bug reproducible
https://bugs.freedesktop.org/show_bug.cgi?id=60958 the greeting text
now tells the requirements for a good report some more clearly.
I recommend to adapt the French
Hi all,
today I corrected a SPAM filter rule with consequence Hold for
moderation; it also caught some Mails what should have been sent to the
mailing list. I hope that now will work correctly.
@Florian:
Please ping me if you find false alerts (I will also check from time to
time).
Best
Florian Reisinger schrieb:
Indeed The message headers matched a filter rule from floeff (and you)...
Hi Florian,
it's important that I can see those mails and check what filter rules
have been matched; only so I can improve the filters. Please ping me if
your find something unexpected in
Hi Rob,
I saw, that I got e-mails concerning my BSA-FR test bug submissions with
CC for French QA list (Bug sur Nouveau dans le BSA français!). Is that
for test affairs or the plan for the general proceeding in future?
It's a French-QA-List decision, but I would not be happy with such
Rob Snelders schrieb:
The French BSA is nearing completion.
Hi Rob,
Great!
I received CC copies of the mails BSA-FR sends to q...@fr.libreoffice.org.
Is there any possibility that BSA checks the ID of the new bug and adds
it including Summary line Mail subject?
Means instadead if
Bug sur
Rob Snelders schrieb:
Hi Rob,
great step, thank you very much
Wrong link [2]? I only find
https://wiki.documentfoundation.org/BugTriage_InProgress/fr
Is that already working?
I tried to submit some Bugs with French BSA UI
* Missing Icon for Android Impress remote
* Login not remembered for
Rob Snelders schrieb:
Can this be added later? Maybe create a bug-report for it for now.
Hi Rob,
yes, or course. I only wanted to mention that so that you have it on the
list, but there is no need to do everything with the first step
Best regards
Rainer
I don't understand what is changed. Why do we want to go from spaces in
a wiki to nbsp
Hi Rob,
the intended main change I did was that I corrected wrong space
encoding % to %20
https://wiki.documentfoundation.org/index.php?title=BugReport_Detailsdiff=64916oldid=64836
With that wrong
Rainer Bielefeld schrieb:
And after that I added a new mistake with the nbsp; due to obsolete
private notes (without thinking about them), some (long) time ago that
was necessary with oLder Wikimedia for getting some templates working.
Hi,
with OLDER Wikimedia, of course.
And I will have
Robinson Tryon schrieb:
If we're pulling data directly from the wiki and using it for the BSA,
should we consider Protecting or semi-Protecting that wiki page?
Hi,
currently it's a more hypothetical problem, there are no violations,
and as you see experience (and may be permissions) is not
Today I corrected a syntax error in the Wiki
https://wiki.documentfoundation.org/index.php?title=BugReport_Detailsdiff=prevoldid=64916
Can someone please update the BSA so that that Component will work?
CU
Rainer
P.S.: In this thread I want to keep you up to date, discussion if
desired
Today I deleted all bugs with Component deletionrequest, what were no
real bug reports, but only tests for BSA or other web infrastructure
issues (or had to be deleted because of confidential contents).
CU
Rainer
P.S.: This thread should keep you up to date, comments or discussion if
Hi all,
it seems that Auto Mime Type recognition is completely broken in Bugzilla
https://bugs.freedesktop.org/show_bug.cgi?id=61845.
Please always correct mime type if necessary after you attached a file,
and please leave a comment in the Bug if your experience is different to
mine.
Joel Madero schrieb:
Hm I have mixed feelings about these requirements.
Hi,
if you answer to my posting 26.02.2013 21:23 you should refer to
https://wiki.documentfoundation.org/QA-FAQ#What_does_it_mean_if_Bugzilla_Field_QA_Contact_is_not_empty.3F
I am thinking about something very simple.
Markus Mohrhard schrieb:
Please mark at least the calc ones as NEW and put perf in the
whiteboard line.
Hi,
except it's rather sure that it's simply a damaged document what can't
be opened by any software.
In all other cases, of course, it's not a crime if we manage it to do a
better
Today I did some cleanup in the SPAM filters, removed duplicates and
invalid mail addresses (it seems the Automatic Moderator functions
forward some faked invalid e-mail addresses to the blacklists).
CU
Rainer
___
List Name: Libreoffice-qa mailing
bfo schrieb:
Adding user (by herself) to QA Contact field would indicate, that this QA
person is actively working on the bug and is responsible either for
Hi,
I added a draft with these ideas in the Wiki
Rainer Bielefeld schrieb:
But to be honest, it's long ago that I read the HeasHack Wiki page,
Well,
currently there on
https://wiki.documentfoundation.org/Development/EasyHacks#Creating_new_EasyHacks
I read New EasyHacks should be created by developers ... Write
EasyHack
Today I deleted all bugs with Component deletionrequest, what were no
real bug reports, but only tests for BSA or other web infrastructure issues.
CU
Rainer
P.S.: This thread should keep you up to date, comments or discussion if
desired please in extra threads to keep this one clear and
Hi,
I believe we should take the chance to find solutions for other Products
/ Components / Subcomponents what currently are a little misplaced in
the Current Bugzilla Product structure:
BUGZILLAASSISTANT
Has not much to do with component WEB, where it currently is placed
INSTALLER GUI
Hi Rob, Hi Marc,
if I remember correctly Marc complained that WWW is not a very good
Bugzilla Component for BSA related issues, and at least I agree with
that assessment. May be following the discussion here will bring up some
better ideas?
Best regards
Rainer
Marc Paré schrieb:
My comment on the BSA Bugzilla component was that, when a bug was filed
for the BSA, that an email/post was sent to the website team.
Hi Marc,
Ah, yes now I remember, THAT was the problem. I also think that that's
not optimum, in more than 90% web team can not help.
Marc Paré wrote:
So, to me, from a user's point of view, I would expect to see the
Impress remote in the Presentation component. It would be the
natural place for me to seek. I don't believe that it would be any
more advantageous to put the Impress remote as a top component.
Hi everyone,
I
Robert Großkopf schrieb:
Hi Robert,
the general condition for NEW is that information the Bug report is
complete and reliable so that a developer can start with hacking without
need to do additional basic research. The most important info is short,
but clear instruction how to reproduce the
Marc Paré schrieb:
I was wondering, would it be possible to make it so that when a bug has
reached the status of Fixed and/or Resolves and/or Closed,
Hi Marc,
I think the way how that can be done most easily is that someone who
maintains the bugs.freedesktop.org account for the mailing list
Hi
Since 2012 I generally add a target info in parenthesis to Bug reports
where the problem vanished and it is not known where exactly the problem
vanished [1]
The advantages of this method:
* Common target:X.Y.Z query string
* Parenthesis shows that there is some unsureness concerning
Hi all,
I had the plan to write down some thoughts concerning your plans to do
an other mass close, but I wasn't in the mood to do that. Due to my
experience with bug wrangling in general and similar actions we did in
LibO Bugzilla, for my personal work I only expect (smaller)
Hi,
I did some emphasis on QA-FAQ
https://wiki.documentfoundation.org/QA-FAQ#How_to_assign_a_bug_.28QA_team_only.29.
I found out that currently we have more than 300 bugs with assignee but
status UNCONFIRMED or NEW [1], most assigned to
cedric.bosdonnat@free.fr, tbehr...@suse.com,
Petr Mladek schrieb:
This will cause many mails only in the first round. It will be normal
level of mails if we do this regularly.
Hi,
That's an illusion, total number of mails will always be the the same.
Only the number of mails per cleanup will be smaller.
BTW, I dislike the noise the
Andras Timar schrieb:
Yes, it is. With msiexec /a you convert the install kit from one
format to another. It is not an installation
Hi,
Yes, but I wonder what can be done with the .msi above the program
folder? I am pretty sure that I was involved in a discussion concerning
reasons of
Hi Kohei,
I see that you changed status of several bugs [1] with you as assignee
from status ASSIGNED to NEW.
My interpretation is that you are intending to do some work on it, but
currently that particular Bug is far at the end of your priority list
and you are not planning activity in
Kohei Yoshida schrieb:
No, those bugs were assigned to me originally by someone else, as part
of the very old workflow. I had no plan to work on them in the first
place.
Hi Kohei,
yes, you are completely right, those assignations were a legacy, and
it's a useful clearing up for those bugs
the problem is at freedesktop.org.
Servers work, I can post Bugzilla comments via Mail interface.
I hope this helps, thank you for your great service.
Best Regards
Rainer Bielefeld
(LibO QA Volunteer)
___
List Name: Libreoffice-qa mailing list
Mail address
Rainer Bielefeld schrieb:
it seems there is a ssl problem with connections to
https://bugs.freedesktop.org/ and may be other services?
Hi,
at least Bugzilla is back, thank you.
Best Regards
Rainer Bielefeld
___
List Name: Libreoffice-qa mailing
klaus-jürgen weghorn ol schrieb:
Hi,
BTW, I prefer to submit a Bug for something like that without asking
here in very most cases:
If it's a bug you saved your time to ask and someone other's to answer.
If it's not a bug someone else not subscribed to the list here will
submit a bug
julien2412 schrieb:
I read quickly this thread,
Hello Julien,
thx, for feedback, I believe for for further discussion of possibly
necessary rethinking of current or planned proceeding we should start a
new thread on libreoffice-qa@lists.freedesktop.org, here we might
discommode devs'
Joel Madero schrieb:
-Status clarification (New vs. Reopened)
**Agreed: *Reopened should only be used if the bug is assigned
*Because of this agreement, modifications have to be made to our current
workflow
-*Agreed: *NEEDINFO: Used only if most the information
Hi all,
just stumbled upon
Today I added new version 3.6.5.2 rc to Bugzilla version picker.
Hi Joel, sorry, please update BSA
CU
Rainer
P.S.: This thread should keep you up to date, discussion if desired
please in extra threads to keep this one clear and short.
___
List
Dan Lewis schrieb:
Can someone do something about the spam that is being sent to
libreoffice-qa@lists.freedesktop.org?
Hi,
yes, and we are doing, but a Spam filter never becomes
ready ... .
CU
Rainer Bielefeld
___
List Name: Libreoffice-qa mailing
Kohei Yoshida schrieb:
Hi all,
I think I understand Joel's intention. I also have problems to find out
whether a bug already is under observation of a developer (because he is
in CC), that was more easy in the early time with very few developers.
And I believe developers should become
Hi all,
I hoped to be able to do lots of tests with 4.0.0.1, but I see a
horrible number of crashes under WIN without any common characteristic,
I can't use this version furthermore for anything similar to normal work.
Any chance that someone suffering from similar problems can contribute
,
result is not satisfying), because Versions from
daily/master/Android-... crashed during installation).
So we need to interest more new additional Hackers helping to create a
LibO Android suite based on the current Master, including Documentation,
Project info, ... .
Best regards
Rainer
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
Rob Snelders schrieb:
Maybe it's good to add that to the wiki:
Hi Rob,
On Rapporter un problème sous LibreOffice
https://wiki.documentfoundation.org/BugReport/fr we already have the
recommendation to ask for assistance at us...@fr.libreoffice.org.
I think requests to
Today I deleted several bugs with this component:
58901 FILEOPEN write protected questionnaire.doc: contents of Input
fields can not be modified
(because of copiright issues with sample document)
Because no real bugs, only created for test affairs:
58633 Extensionname: test
58632
Hi,
I agree with the arguments here. My conclusion: if tehere is a relevant
Number of early adopters, who might find the Feedback item in Help menu,
we should have something in BSA finding the appropriate Hardware-OS
combination (may be with additional hint in comment). This
combination(s)
Petr Mladek schrieb:
there have been created the libreoffice-4.0.0.0.beta2 tag.
Hi all,
again a problem with the WIN build?
CU
Rainer
___
List Name: Libreoffice-qa mailing list
Mail address: Libreoffice-qa@lists.freedesktop.org
Change settings:
automated proceeding (mail to
mailing lists or whatever), If you have ideas we should discuss that,
and me or Joel can do the necessary administration in bugzilla.
Best regards
Rainer Bielefeld
___
List Name: Libreoffice-qa mailing list
Mail address
Hi all,
we have LibO also running on Android OS and Raspberry Pi hardware. What
do you think, should we have these environments explicitly in Bugzilla?
Discussion please on libreoffice-qa@lists.freedesktop.org!
Best regards
Rainer Bielefeld
(QA Volunteer
are working on all core functions.
In any case we should leave a comment on
https://wiki.documentfoundation.org/BugReport_Details whether reports
are useful and if yes, how they should be done).
@Rene, what are your needs?
Best regards
Rainer Bielefeld
(QA Volunteer
Hi all,
I saw this AOOo issue on my ticker:
https://issues.apache.org/ooo/show_bug.cgi?id=121406
Is there need for action with LibO, too?
CU
Rainer
___
List Name: Libreoffice-qa mailing list
Mail address: Libreoffice-qa@lists.freedesktop.org
Change
want to report a bug or an enhancement request please use LibO
menu 'Help - Feedback'.
Best regards
Rainer Bielefeld
(QA-volunteer)
___
List Name: Libreoffice-qa mailing list
Mail address: Libreoffice-qa@lists.freedesktop.org
Change settings: http
Today I added 4.1.0.0.alpha0+, because we have new 4.1 Master Version
since some days and the plan was to add a new Master Version to Bugzilla
for every new major release (x.0, x.1, x.2, x.3, ...).
CU
Rainer
P.S.: This thread should keep you up to date, comments or discussion if
desired
regards
Rainer Bielefeld
(QA-Volunteer)
___
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
Today I deleted all bugs with Component deletionrequest, what were no
real bug reports, but only tests for BSA or other web infrastructure issues.
CU
Rainer
P.S.: This thread should keep you up to date, comments or discussion if
desired please in extra threads to keep this one clear and
Bjoern Michaelsen schrieb:
Do you have a bug# by chance? I only found:
https://bugs.freedesktop.org/show_bug.cgi?id=48878
Hi,
yes, that would help, I did a query [1] and found bugs:
*52275* CRASH - Using Mysql native connector extension and ODB file when
passing connection identifiers
Hi all,
can you all please test whether Extensions (and templates) from
http://extensions.libreoffice.org/
you have been used to install with LibO 3 also work with LibO 4?
If you have permissions, please update Versions info of the extensions,
if not please leave a comment (if you have to tell
Hi all,
in this thread please leave your results if you are not willing to
participate the collaboration test.
Pleas only leave a brief report with your results, do not discuss here,
we want to keep the thread short and clear.
Best Regards
Rainer
Woks fine with parallel installation of LOdev 4.0.0.0.alpha1 -
ENGLISH UI / German Locale [Build ID: dec8fe)] {tinderbox: @6, pull
time 2012-11-13 06:07:28} on German WIN7 Home Premium (64bit) with
separate /4 User Profile for Master Branch
CU
Rainer
P.S.: Pleas only leave a brief
1 - 100 of 277 matches
Mail list logo
