Re: [Libreoffice-qa] minutes of LibreOffice QA call 2012-03-09 15:00 UTC

Hi Bjoern, On Fri, Mar 09, 2012 at 06:42:45PM +0100, Bjoern Michaelsen wrote: > Hi all, > > here are the minutes of the QA call 2012-03-09 15:00 UTC > > attendants: Cor, Ivan, Rainer, Markus, Michael, Korrawit, Petr, Kendy, > Bjoern + Yifan :) Thanks for the minutes and pushing on everything.

Re: [Libreoffice-qa] Migrationsleitfaden des Bundes (Migration Guide)

> > Concerning mentioned bugs and problems I will try to find out whether >> already known, but descriptions are rather rare. >> > > Would be great if people with (specific) bugs could be encouraged to > submit / mention them precisely in our neat bugtracker :-) > Seems like #34423

[Libreoffice-qa] DrMemory howto (for Windows) ...

Hi guys, So - if you have a crasher bug on Windows, and the stack trace is inside 'malloc' or 'free' or 'new' or 'delete' then most likely you have a memory corruption - often intermittent bugs are these too. For these cases, there is a wonder-new-tool (for Windows), called DrMemo

Re: [Libreoffice-qa] Migrationsleitfaden des Bundes (Migration Guide)

Rainer Bielefeld wrote (07-03-12 17:04) Rating for LibreOffice is benevolent, but not enthusiastic, may be you should know on CeBit. Good thing is that LibreOffice is used as an indicating name for LibreOffice and OpenOffice.org (in at least one section) Concerning mentioned bugs and proble

Re: [Libreoffice-qa] [ANN] LibreOffice 3.4.6 RC2 test builds available

Bjoern Michaelsen schrieb: We need to be sure to detect and pinpoint regressions earlier and more precise than in 3.4 Hi, That's at least an important part of the truth, when 3.4.0 release came only 15 regressions were known (bud keyword handling was very arbitrary in those days). Let's h

Re: [Libreoffice-qa] [ANN] LibreOffice 3.4.6 RC2 test builds available

Hi Pedro, On Wed, Mar 14, 2012 at 05:32:04PM +, Pedro Lino wrote: > Maybe branch 3.4.x should continue to be updated (in the same way that > Mozilla keeps fixing bugs in version 3.6.x, with x currently at 28, even > though the latest version is 11.0...) until at least all 3.3.x regressions > a

Re: [Libreoffice-qa] [ANN] LibreOffice 3.4.6 RC2 test builds available

Pedro Lino schrieb: Maybe branch 3.4.x should continue to be updated (in the same way that Mozilla keeps fixing bugs in version 3.6.x, Hi, Yes, something like that would be great, but we should not underrate the work that such a proceeding would cost. But I believe I we have some kind of gu

Re: [Libreoffice-qa] [ANN] LibreOffice 3.4.6 RC2 test builds available

Hi Rainer, On Wed, Mar 14, 2012 at 05:48:17PM +0100, Rainer Bielefeld wrote: > We still have 45 unfixed regressions compared to 3.3, Lifecycle of > 3.4 will end with 3.4.6(?), so this version is more or less useless > for most (or at least very many) 3.3 or 3.4 users. While I agree that 45 regres

Re: [Libreoffice-qa] [ANN] LibreOffice 3.4.6 RC2 test builds available

Hi Rainer, all It's my belief that we will have to rethink our release concept. > It is true that this model tends to accumulate regressions. Unfortunately it is not easy to measure if adding more features is attracting more users than repelling users because of regressions/unsolved problems...

Re: [Libreoffice-qa] [ANN] LibreOffice 3.4.6 RC2 test builds available

Fridrich Strba schrieb: for 3.4.6 RC2, we're now uploading builds to a public (but non-mirrored - so don't spread news too widely!) place, as soon as they're available. Grab them here: If you've a bit of time, please give them a try& report *critical* bugs not yet in bugzilla here, Hi, w

Re: [Libreoffice-qa] tag for bugs related to experimental turned on/off

On Wed, Mar 14, 2012 at 11:04:55AM -0400, Terrence Enger wrote: > After thinking about it, I agree. Net result of wiki edits: > Thanks! Best, Bjoern __

Re: [Libreoffice-qa] tag for bugs related to experimental turned on/off

On Tue, 2012-03-13 at 16:51 +0100, Bjoern Michaelsen wrote: > On Tue, Mar 13, 2012 at 03:18:17PM +0100, Cor Nouws wrote: > > IMO, we need a tag for bugs related to experimental turned on/off > > See comment https://bugs.freedesktop.org/show_bug.cgi?id=43869#c24 > > > > What is useful? whiteboard,

[Libreoffice-qa] [ANN] LibreOffice 3.4.6 RC2 test builds available

Hi *, for 3.4.6 RC2, we're now uploading builds to a public (but non-mirrored - so don't spread news too widely!) place, as soon as they're available. Grab them here: http://dev-builds.libreoffice.org/pre-releases/ If you've a bit of time, please give them a try & report *critical* bugs not yet

Re: [Libreoffice-qa] tag for bugs related to experimental turned on/off

On Tue, Mar 13, 2012 at 08:25:11PM +0100, Cor Nouws wrote: > >A feature is either stable enough to be included even with "experimental > >enabled" or it is not. If you care about macros, help out getting it stable > >enough to be moved out of "experimental" an into the general feature set. > > Hmm

Re: [Libreoffice-qa] [ANNOUNCE] libreoffice-3.5.1.2 tag created (3.5.1-rc2)

Hi Tommy, On Wed, 2012-03-14 at 09:39 +0100, Tommy wrote: > > there have been created the libreoffice-3.5.1.2 tag for 3.5.1-rc2 > > release. > > Hi, is the RC2 going to be released "bit-per-bit" as 3.5.1 final? In the absence of any horrors I would expect that :-) > on the release plan

Re: [Libreoffice-qa] tag for bugs related to experimental turned on/off

Pedro Lino wrote (14-03-12 08:40) Do you mean you are going to add an option to enable Macro separately from the rest of the experimental features? That is great! I expect I can achieve that yes. "How to activate macros" is a quite common question from users so I think that would be a welcom

Re: [Libreoffice-qa] tag for bugs related to experimental turned on/off

Hi Cor, all So an easy and sort of logic solution is to have an option to turn Macro > recording of for those that want that. > I think I can take this one > Do you mean you are going to add an option to enable Macro separately from the rest of the experimental features? That is great! "How

Re: [Libreoffice-qa] tag for bugs related to experimental turned on/off

Cor Nouws wrote (13-03-12 20:25) It looks logic to suggest that people that are too unhappy with current macro-recording functionality, stand up to improve it, rather then to hide it, and with the same strike, expose people that do use the recording to undocumented risks. So an easy and sort o