Re: [Libreoffice-qa] [ANN] LibreOffice 4.0.3 RC1 test builds available

Hi Marc, I am not sure if anyone has responded this yet. Marc Kaulisch píše v St 17. 04. 2013 v 18:28 +0200: > With this version Symantec (Norton Internet Security) is not very happy > with LibreOffice :-( > > I get the following notice and will contact Symantec. This was the best solution. It

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

Joel Madero píše v Ne 21. 04. 2013 v 09:32 -0700: > Some other content that will be on the page is a general overview of QA > work, how to's for things like our mailing list and #libreoffice-qa IRC > channel, and OS specific content such as parallel installs on different > OS' (required for tria

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

Latest build still has the Writer problem. The About box is fixed. Version: 4.1.0.0.alpha0+ Build ID: 6536d0eb4f56e64c9b74b358642e3ee1e39353e TinderBox: Win-x86@6, Branch:master, Time: 2013-04-23_04:48:50 -- View this message in context: http://nabble.documentfoundation.org/fdo-63680-Windows-b

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] After EOL has been reached...

Robinson Tryon píše v Pá 19. 04. 2013 v 17:21 -0400: > Per discussion at the meeting today, we generally agreed to the following: > > AGREED: For users inquiring about tech support after the EOL date of a > release, we politely indicate that the release is EOL and ask them to > upgrade to a new ve

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

Hi Rainer, all Rainer Bielefeld-2 wrote > thank you for your research, but please do no spread discussion to > anywhere, this list is explicitly NOT for bug discussions, > ;, and > info > here in the list might be missing in the bug

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

Hi Rainer, Understand the perceived constraint to using the list. And while I can't answer for Pedro, 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? I am

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] fdo#63680 - Windows builds of Master - Writer crashing

Hi, On Tue, Apr 23, 2013 at 04:35:25AM -0700, Pedro wrote: > The bugzilla comments are not a place for discussion. The bugzilla comments are the place to add information that helps cornering the bug (e.g. triaging when it first appeared). > The User list is obviously not a place to discuss bugs.

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

Hi Bjoern, all Bjoern Michaelsen wrote > How do you want to discuss a bug in a productive way, that neither helps > QA or > devs (thus the first) or the users (thus the second)? The question is not How but Where to discuss (which is NOT the same as comment)? I think the QA list is the place to

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

Rainer Bielefeld-2 wrote > ...a Link (in the Bug) to the thread in the archive might be useful... Agreed, and done... -- View this message in context: http://nabble.documentfoundation.org/fdo-63680-Windows-builds-of-Master-Writer-crashing-tp4051683p4051801.html Sent from the QA mailing list a

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

Hi :) I finished reading this topic now, so my two cents Am Dienstag, 23. April 2013 15:37:41 schrieb Pedro: Hi Bjoern, all Bjoern Michaelsen wrote How do you want to discuss a bug in a productive way, that neither helps QA or devs (thus the first) or the users (thus the second)? Th

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

On Tue, Apr 23, 2013 at 06:37:41AM -0700, Pedro wrote: > Bjoern Michaelsen wrote > > How do you want to discuss a bug in a productive way, that neither helps > > QA or > > devs (thus the first) or the users (thus the second)? > > The question is not How but Where to discuss (which is NOT the same

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

Hi :) As I am the coordinator for the qa.libreoffice.org launch, I would like to make a QA for QA section (Questions and answers for quality assurance. The page-name is different, of course). So, if you have a question, which you thing would be appropriate for "QA for QA", please add it to yo

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

On Tue, Apr 23, 2013 at 04:26:34PM +0200, Florian Reisinger wrote: > As I am the coordinator for the qa.libreoffice.org launch, I would > like to make a QA for QA section (Questions and answers for quality > assurance. The page-name is different, of course). So, if you have a > question, which you

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

Hi Florian I think it is better FAQ for QA More questions * Can I have several versions of LibreOffice in parallel? *Is there an easy way to filter bugs (e.g. by OS and/or application and/or status)? -- View this message in context: http://nabble.documentfoundation.org/Libreoffice-qa-FAQ-for

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] After EOL has been reached...

On Tue, Apr 23, 2013 at 7:30 AM, Petr Mladek wrote: > Robinson Tryon píše v Pá 19. 04. 2013 v 17:21 -0400: > > 6 months sounds fine to me for most of the bugfix releases. > > Well, I would suggest to leave either the last bugfix release or some > generic version, e.g. 3.5, 3.4, 3.3 longer time. We

[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] 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

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

Hi, I totally agree and closed my bug(s) created today... What should I do with my test case? Am 23.04.2013 17:41, schrieb Rainer Bielefeld: Florian, what do you think? CU Rainer -- Liebe Grüße, / Yours, Florian Reisinger ___ List Name: Libreof

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

On Tue, Apr 23, 2013 at 12:13 PM, Rainer Bielefeld wrote: > > not good! We will not create complicated wrong rules for things what are > easy to understand. My "rule" was 1 short sentence long. Compared to the current morass of QA documentation, I don't think it's appropriate to call that "compli

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] Addressing regressions within a release

First apologies that I've not answered this earlier :) Trying to get better about reading my digest. > One good way to tackle this problem would be to bibisect any bug > marked as a regression and try to date it to before the X.X.0 point > release. > > Joel - How much work would it be to bibisect

Re: [Libreoffice-qa] Addressing regressions within a release

On Tue, Apr 23, 2013 at 1:56 PM, Joel Madero wrote: >> Joel - How much work would it be to bibisect the regressions for each >> release? Aside from initial triage/repro, what other QA tasks should >> take priority over this work? > > > For major releases not a problem but for minor releases more o

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

> > -- Forwarded message -- > From: Robinson Tryon > To: Petr Mladek > Cc: LibreOffice-QA > Date: Tue, 23 Apr 2013 11:34:45 -0400 > Subject: Re: [Libreoffice-qa] After EOL has been reached... > On Tue, Apr 23, 2013 at 7:30 AM, Petr Mladek wrote: > > Robinson Tryon píše v Pá 19.

[Libreoffice-qa] Bugs that need triaged ASAP - Potential Regressions within Release

This is a list of bugs that get highest priority for getting triaged[1]. This will help us tremendously. For procedures on how to correctly triage the bug please see link[2]. [1] https://bugs.freedesktop.org/report.cgi?x_axis_field=resolution&y_axis_field=version&z_axis_field=&query_format=report

Re: [Libreoffice-qa] Addressing regressions within a release

On Tue, Apr 23, 2013 at 10:56:20AM -0700, Joel Madero wrote: > For major releases not a problem but for minor releases more of a problem > because bibisect is only updated per major release. Actually I updated bibisect to work on the source tags (*): https://gerrit.libreoffice.org/gitweb?p=core.

Re: [Libreoffice-qa] Addressing regressions within a release

On 04/23/2013 01:46 PM, Bjoern Michaelsen wrote: On Tue, Apr 23, 2013 at 10:56:20AM -0700, Joel Madero wrote: For major releases not a problem but for minor releases more of a problem because bibisect is only updated per major release. Actually I updated bibisect to work on the source tags (*):