[Libreoffice-qa] Role of the QA calls

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 c

Re: [Libreoffice-qa] Streamlining & Improving Triage Efforts

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 done.

Re: [Libreoffice-qa] Writer Printing Bugs with LibO 4

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 docum

Re: [Libreoffice-qa] After EOL has been reached...

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

[Libreoffice-qa] Writer Printing Bugs with LibO 4

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",

Re: [Libreoffice-qa] FAQ for qa.libreoffice.org

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 Qa-Contact-field

Re: [Libreoffice-qa] fdo#63680 - Windows builds of Master - Writer crashing

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 in

Re: [Libreoffice-qa] [libreoffice-marketing] Re: New QA Site - Press Release?

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

Re: [Libreoffice-qa] fdo#63680 - Windows builds of Master - Writer crashing

V Stuart Foote schrieb: Would help to know if this is affecting only this TB, or if it is affecting all Windows builds. Hi Stuart, Pedro, thank you for your research, but please do no spread discussion to anywhere, this list is explicitly NOT for bug discussions,

Re: [Libreoffice-qa] New text for NEEDINFO Changes

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 vari

Re: [Libreoffice-qa] After EOL has been reached...

Robinson Tryon schrieb: Per discussion at the meeting today, we generally agreed to the following: Hi, I left some hints and thoughts on . CU Rainer ___ List Name: Libreoffice-qa

Re: [Libreoffice-qa] [LibreOffice-QA] Conference Call 2013-04-19 - Agenda & Minutes

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 g

Re: [Libreoffice-qa] mailing list administration - SPAM Sender Filters

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 _

Re: [Libreoffice-qa] mailing list administration - SPAM Filters

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 mai

Re: [Libreoffice-qa] Question : FILEOPEN bug vs 'filters and storage' bug

Jochen schrieb: Why should other user be prevented from checking and confirming? Hi, well, they will be discouraged and deterred (because the have no idea concerning what problem that report might be), not prevented. Best regards Rainer ___ Lis

Re: [Libreoffice-qa] Question : FILEOPEN bug vs 'filters and storage' bug

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 no

Re: [Libreoffice-qa] BSA and Component WWW->Sub-component

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: Best regards Rainer ___

Re: [Libreoffice-qa] Stagnant NEEDINFO bugs

Hi, just for the records: More or less with the beginning of April, I started to check Stagnant NEEDINFO bugs without change for more than 6 months where I am involved. My goal is to handle at least 5 bugs per week. Statistics 2013-04-17 Number Percent comment

Re: [Libreoffice-qa] Version in fdo version picker for SI-GUI

Hi Florian Here a quick solution keeping the current "Extensions" Component with correct Bugzilla Syntax you see on until we have a final decision. Unfortunately (of course) the "SI-GUI" name will break consistence with older

Re: [Libreoffice-qa] Version in fdo version picker for SI-GUI

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 ___

Re: [Libreoffice-qa] Version in fdo version picker for SI-GUI

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 Co

[Libreoffice-qa] How to exclude Bugzilla "Sub Components" from BSA

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 "Tinderb

Re: [Libreoffice-qa] Bugzilla administration info - 3.3 non releases removed from Version Selector

As announced here 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 vers

Re: [Libreoffice-qa] Lifecycle of builds?

Robinson Tryon wrote: Rainer described this as "not-release-3.3 [builds]". I think we're mostly in agreement Hi Robinson, I hope so. Priority for decisions how to use the Versions Picker are developers' needs, and their interest (as Michael stated) is to find out where the bug appeared (for

Re: [Libreoffice-qa] Lifecycle of builds?

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 the

Re: [Libreoffice-qa] Lifecycle of builds?

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 <

Re: [Libreoffice-qa] Removing LibO 3.3 from Versions dropdown in Bugzilla

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 ina

[Libreoffice-qa] Removing LibO 3.3 from Versions dropdown in Bugzilla

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 [

Re: [Libreoffice-qa] How to change QA processes: was: What should we do with bugs filed against Extensions/Templates?

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 pro

Re: [Libreoffice-qa] BSA WWW component

Marc Paré schrieb: Just wondering, should a sub-component "LibreOffice site" be in the list? Everything else seems to be in the list. Hi Marc, currently we have all that under "TDF Site" (historical reasons from the early days), what indeed might be worrying, many BSA users might never have

Re: [Libreoffice-qa] Bugzilla administration info - Help for

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 defin

Re: [Libreoffice-qa] Header of the Print Dialog: Localisation?

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: http://lists.freedesktop.org/mailman/listinfo/

Re: [Libreoffice-qa] New Bugzilla Version warning

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 fo

Re: [Libreoffice-qa] Bugzilla administration info - New Version 3.6.6.2 rc

Today I added new version 3.6.6.2 rc to Bugzilla version picker. Hi Joel, 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 Name: L

Re: [Libreoffice-qa] New Bugzilla Version warning

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

Re: [Libreoffice-qa] New Bugzilla Version warning

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.

Re: [Libreoffice-qa] Bugzilla administration info - Help for

Today I added full syntax BSA Help to the Wiki on . 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

Re: [Libreoffice-qa] Bugzilla administration info - Impress Remote Versions

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

Re: [Libreoffice-qa] Bugzilla administration info - Impress Remote Versions

Today I removed the Impress Remote Versions from Bugzilla. Proceeding until a final Solution for bug handling with LibO related tools: Like with Enhancements CU Rainer P.S.: In this thread I want to

[Libreoffice-qa] New Bugzilla Version warning

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 li

Re: [Libreoffice-qa] How to report Enhancement Requests for FDO infrastructure (Bugzilla)

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.freedeskt

Re: [Libreoffice-qa] Wiki pages cruft cleanup

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 Name:

[Libreoffice-qa] How to report Enhancement Requests for FDO infrastructure (Bugzilla)

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

Re: [Libreoffice-qa] Bugzilla administration info - Component 'Extensions'

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 Andre

Re: [Libreoffice-qa] What should we do with bugs filed against Extensions/Templates?

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

Re: [Libreoffice-qa] What should we do with bugs filed against Extensions/Templates?

Robinson Tryon schrieb: In our last QA Meeting we discussed what we should do with bugs filed against Extensions or Templates. Hi all, did I miss something? Do we have a problem? 1. Close as NOTOURBUG + comment to contact extensions author No, that is not a good Idea. Bugzilla is the requ

Re: [Libreoffice-qa] French bug in Bugzilla

Robinson Tryon schrieb: It looks like that bug was submitted via the BSA. Perhaps we need to be more explicit in the BSA about authoring bugs in English? Hi, Please see I do not know the current status of the BSA-FR what will create mails t

Re: [Libreoffice-qa] French bug in Bugzilla

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 told on this list that he is willing to translate reports in French language, from time to time I ask him for he

Re: [Libreoffice-qa] Priorizing Chart

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 av

[Libreoffice-qa] Priorizing Chart

Hi Joel, I left some thoughts how to refine the "How to Priorize" chart on Can you contribute the source document so that I can * do some changes to have the chart some more confirming to standards * In a second

Re: [Libreoffice-qa] Explanations on the NL BSA purpose

Hi Sophie, with the fix for "Bug 60958 BUGZILLAASSISTANT: Greeting text should tell that goal is to make bug reproducible" the greeting text now tells the requirements for a good report some more clearly. I recommend to adapt the French gr

Re: [Libreoffice-qa] mailing list administration - SPAM Filters

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

Re: [Libreoffice-qa] Explanations on the NL BSA purpose

Sophie Gautier schrieb: Hi all, So I'll try first to explain my idea clearly on the workflow we have thought about: Hi Sophie, thanks a lot, I see that all my concerns were unnecessary, I simply did not have information how that should work. Is there already a plan how BSA-FR will be rea

Re: [Libreoffice-qa] mailing list administration

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

Re: [Libreoffice-qa] Fwd: Fwd: Bug sur Nouveau dans le BSA français!

Robinson Tryon schrieb: Rainer - I'm a little confused by the process you describe, but I think I understand the gist of it. Hi Robinson, it's more some kind of loud thinking than a final, ready idea. I really like the idea of having the original bug submitter being listed as the bug repor

Re: [Libreoffice-qa] Fwd: Fwd: Bug sur Nouveau dans le BSA français!

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

Re: [Libreoffice-qa] Fwd: Fwd: Bug sur Nouveau dans le BSA français!

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 addi

Re: [Libreoffice-qa] Fwd: Fwd: Bug sur Nouveau dans le BSA français!

Rob Snelders schrieb: Hi Rob, great step, thank you very much Wrong link [2]? I only find Is that already working? I tried to submit some Bugs with French BSA UI * Missing Icon for Android Impress remote * Login not remembered fo

Re: [Libreoffice-qa] Fwd: Fwd: Bug sur Nouveau dans le BSA français!

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 ___

Re: [Libreoffice-qa] BUGZILLAASSISTANT broken due to   in Component names

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

Re: [Libreoffice-qa] BUGZILLAASSISTANT broken due to   in Component names

Rainer Bielefeld schrieb: And after that I added a new mistake with the " " 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

[Libreoffice-qa] BUGZILLAASSISTANT broken due to   in Component names

I don't understand what is changed. Why do we want to go from spaces in a wiki to   Hi Rob, the intended main change I did was that I corrected wrong space encoding "%" to "%20" With that wrong e

Re: [Libreoffice-qa] Bugzilla administration info - BUGZILLAASSISTANT

Today I corrected a syntax error in the Wiki 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

Re: [Libreoffice-qa] mailing list administration

Hi Florian, today I added some SPAM filter Rules with consequence "Hold for moderation". Please tell me if you suffer from too many false alerts. Best regards Rainer ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freed

Re: [Libreoffice-qa] Bugzilla administration info - New Version "(See in Summary)"

Today I created a new Version for the Picker "(See in Summary)". Explication: CU Rainer P.S.: This thread should keep you up to date, d

Re: [Libreoffice-qa] Bugzilla administration info - deletionrequest

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 desi

[Libreoffice-qa] Please consider Bug 61845 - Attachment ODF document" recognized as "text/plain" by auto detect.

Hi all, it seems that Auto Mime Type recognition is completely broken in Bugzilla . 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. Discu

Re: [Libreoffice-qa] Should we use the "QA Contact" field?

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 I am thinking about something very simple.

Re: [Libreoffice-qa] Accepting "can't open"-bugs even if original program fails?

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 job

Re: [Libreoffice-qa] mailing list administration

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 li

Re: [Libreoffice-qa] Should we use the "QA Contact" field?

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

Re: [Libreoffice-qa] LibreOffice 4.0.1 RC1 - QA special requests ...

Michael Meeks schrieb: So - I can only encourage people to test these things; Hi Michael, I had hoped that it would be possible to use the RC for productive work and so to find some bugs what only become visible in "real life", but not during standard tests. Unfortunately currently

Re: [Libreoffice-qa] [Libreoffice-ux-advise] EasyHack proposals

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

Re: [Libreoffice-qa] Bugzilla administration info

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 sh

Re: [Libreoffice-qa] Bugzilla Integration of Impress remote control - Versions

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

Re: [Libreoffice-qa] Bugzilla Integration of Impress remote control - Related problems - BUGZILLAASSISTANT

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. Unfort

Re: [Libreoffice-qa] Bugzilla Integration of Impress remote control - Related problems - BUGZILLAASSISTANT

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

Re: [Libreoffice-qa] Bugzilla Integration of Impress remote control - Related problems

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 Flori

Re: [Libreoffice-qa] Bugzilla Integration of Impress remote control - Versions

Hi, I am not happy with the solution that we have the AIR Versions simply added to the LibO verions picker. That is some kind of precendent and might encourage also to add Versions for Dictionaries and what ever else there. Please also see [Bug 60766] BUGZILLA: Remove Android Impress Remote V

[Libreoffice-qa] Bugzilla Integration of Impress remote control

Hi, I believe the current ad hoc solution for the Bugzilla integration of "Impress remote control" still needs some discussion. Let's do it here. CU Rainer ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.or

Re: [Libreoffice-qa] Bugs and "Fixed" "Resolved" "Closed" status

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

Re: [Libreoffice-qa] What are the requirements to set a bug to "NEW"

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 p

[Libreoffice-qa] Target information for Status WORKSFORME

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 accur

Re: [Libreoffice-qa] Stagnant NEEDINFO bugs

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) complications,

Re: [Libreoffice-qa] Bugs with assignee but status NEW

Hi, I did some emphasis on QA-FAQ . 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, r...@

Re: [Libreoffice-qa] Stagnant NEEDINFO bugs

Petr Mladek schrieb: Well, I am still not persuaded that we want 2 or more strike solution. Hi Petr, me too! This mailing with automated personal mails is my compromise offer. And I have little hope to get some feedback for those 1/3 real bugs I observed in a sample before the last "Big clo

Re: [Libreoffice-qa] Stagnant NEEDINFO bugs

Pedro schrieb: I think that is extremely rude. It reminds me of my Graduation diploma which was not ready for 3 years and then I received a postcard saying I had 10 days to pick it up... Hi, no, we will not leave open a pending action item for 1 month. During that time several of the relate

Re: [Libreoffice-qa] Stagnant NEEDINFO bugs

Petr Mladek schrieb: IMHO, the most important is to give user chance to answer before the first warning (30 days or so). Hi Petr, I don't think so. My experience is that the reporter normally will answer within 3 days (mostly: latest next day) or never. We should not base our decisions on 1

Re: [Libreoffice-qa] Question about BUG 54206 fix for v.4.0

Florian Effenberger schrieb: I miss the plot on this - which readme are you talking about? ;) Hi Florian, we talk about THE readme.txt of each LibO build, with WIN I see it in the readmes folder folder, in a Dev Builds it's the only readme.txt there. CU Rainer

Re: [Libreoffice-qa] Stagnant NEEDINFO bugs

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

Re: [Libreoffice-qa] installing 400rc2 parallel on Windows - no way to choose extensions ?

Andras Timar schrieb: You can install LibreOffice with that .msi. It works the same as the original. Hi András, I tried with one of my 4.1.0.0 server installations on WIN: 1. launched master~2013-01-24_22.52.49_LibO-Dev_4.1.0.0.alpha0_Win_x86.msi 2. Custom Installation 3. Unselected Writ

Re: [Libreoffice-qa] installing 400rc2 parallel on Windows - no way to choose extensions ?

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 that

Re: [Libreoffice-qa] Stagnant NEEDINFO bugs

Joel Madero schrieb: Hi Joel, thank you for opening this discussion with your thoughts and suggestions. To avoid misunderstandings: my critics at current plans does not mean that I do not want any automated mass cleanups. I would appreciate to get rid of lots of hopeless reports with few "cos

Re: [Libreoffice-qa] Question about BUG 54206 fix for v.4.0

Marc Paré schrieb: Do we really need a copy of the readme on the site? Hi Marc, I also doubt that such copy is necessary. If we need it because of legl reasons, we need a TOC with links to readme files in all available languages and for all different public versions. If we do not need su

Re: [Libreoffice-qa] Bugs with assignee but status NEW

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 t

[Libreoffice-qa] Bugs with assignee but status NEW

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 near

Re: [Libreoffice-qa] SSL problem?

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: Libreoff

[Libreoffice-qa] SSL problem?

her user, so I think 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

Re: [Libreoffice-qa] Bugzilla administration info - New 4.0.0.2 rc

Today I added new version 4.0.0.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 Na

Re: [Libreoffice-qa] Version number for 4.0 RC2

Michael Stahl schrieb: where do you see this number? it's probably my fault but in the About dialog it looks right here in my build... Hi, "Bug 59798 - CONFIGURATION: Wrong Version info 4.0 .0.2" CU Rainer __

  1   2   3   4   5   >