Re: [Libreoffice-qa] [ANN] Referencing bugs in commits

2012-02-14 Thread Markus Mohrhard
Hey, 2012/2/14 Michael Stahl : > On 14/02/12 17:48, Andras Timar wrote: >> 2012/2/14 Ivan Timofeev : >>> On 14.02.2012 19:31, Michael Meeks wrote: On Tue, 2012-02-14 at 16:16 +0100, Jan Holesovsky wrote: > > Markus has implemented a nice feature that should help keeping the

Re: [Libreoffice-qa] RC3 released as Final version???

2012-02-14 Thread Luc Castermans
Hi, YES!! RC3 etc. should be removed from the About. Indeed marketing wise this it is bad to keep RC3 while the product is flagged as 3.5. regards Luc 2012/2/15 Rimas Kudelis : > 2012.02.15 00:14, Pedro rašė: > >> Olav Dahlum wrote >>> >>> This should be fixed ASAP from a marketing point of

Re: [Libreoffice-qa] RC3 released as Final version???

2012-02-14 Thread Rimas Kudelis
2012.02.15 00:14, Pedro rašė: Olav Dahlum wrote This should be fixed ASAP from a marketing point of view. It's all about expectations, so renaming the tarball etc is just not good enough. Leif did also receive a similar complaint earlier, so this should be taken very seriously. This is not the f

Re: [Libreoffice-qa] RC3 released as Final version???

2012-02-14 Thread Olav Dahlum
2012/2/14 Pedro > > Olav Dahlum wrote > > > > This should be fixed ASAP from a marketing point of view. It's all about > > expectations, so renaming the tarball etc is just not good enough. > > Leif did also receive a similar complaint earlier, so this should be > > taken very seriously. This is

Re: [Libreoffice-qa] RC3 released as Final version???

2012-02-14 Thread Pedro
Olav Dahlum wrote > > This should be fixed ASAP from a marketing point of view. It's all about > expectations, so renaming the tarball etc is just not good enough. > Leif did also receive a similar complaint earlier, so this should be > taken very seriously. This is not the first time I've addres

Re: [Libreoffice-qa] RC3 released as Final version???

2012-02-14 Thread Olav Dahlum
On 14/02/12 22:35, Cor Nouws wrote: > Pedro wrote (14-02-12 22:33) > >> is released and the About box says >> >> LibreOffice 3.5.0rc3 > > IIRC, this is as usual: after the final RC no new builds are made, so no > strings are updated :-) > > This should be fixed ASAP from a marketing point of v

Re: [Libreoffice-qa] RC3 released as Final version???

2012-02-14 Thread Cor Nouws
Pedro wrote (14-02-12 22:33) is released and the About box says LibreOffice 3.5.0rc3 IIRC, this is as usual: after the final RC no new builds are made, so no strings are updated :-) -- - Cor - http://nl.libreoffice.org ___ List Name: Libreoff

[Libreoffice-qa] RC3 released as Final version???

2012-02-14 Thread Pedro
Hi all, I am aware that for developers a .0 release is a little more than a Beta, but for QA people I think that it is a little offensive that a Final version is released and the About box says LibreOffice 3.5.0rc3 Maybe QA has a different meaning for me. But it really pisses me off the lack of

Re: [Libreoffice-qa] Bugzilla Page view - comment text line length

2012-02-14 Thread Cor Nouws
Rainer Bielefeld wrote (14-02-12 19:23) Hello, I have been used to see Bugzilla respecting my screen width, for nearby all bugs Bugzilla line length for the comments matched with my screen width. Some days ago behavior changed, Page heading and footer still [...] I Can't find settings to modi

Re: [Libreoffice-qa] [ANN] Referencing bugs in commits

2012-02-14 Thread Michael Stahl
On 14/02/12 17:48, Andras Timar wrote: > 2012/2/14 Ivan Timofeev : >> On 14.02.2012 19:31, Michael Meeks wrote: >>> >>> >>> On Tue, 2012-02-14 at 16:16 +0100, Jan Holesovsky wrote: Markus has implemented a nice feature that should help keeping the bugs up to date: whenever you are co

Re: [Libreoffice-qa] [ANN] Referencing bugs in commits

2012-02-14 Thread Jan Holesovsky
Hi Ivan, Ivan Timofeev píše v Út 14. 02. 2012 v 20:33 +0400: > Is it possible somehow include the information about a target version? Oh - great idea :-) Added that to the script; it does some best-effort guess, by saying "It will be available in LibreOffice x.y.z.", where x.y is derived from t

Re: [Libreoffice-qa] Bugzilla Page view - comment text line length

2012-02-14 Thread Rainer Bielefeld
Hi, I forgot to mention, search result still are shown in a perfect way. ATB Rainer ___ List Name: Libreoffice-qa mailing list Mail address: [email protected] Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffic

[Libreoffice-qa] Bugzilla Page view - comment text line length

2012-02-14 Thread Rainer Bielefeld
Hello, I have been used to see Bugzilla respecting my screen width, for nearby all bugs Bugzilla line length for the comments matched with my screen width. Some days ago behavior changed, Page heading and footer still match perfectly with screen width, but now the text lines of comments are m

Re: [Libreoffice-qa] [ANN] Referencing bugs in commits

2012-02-14 Thread Jan Holesovsky
Hi Pierre-André, Pierre-André Jacquod píše v Út 14. 02. 2012 v 18:02 +0100: > > The bug reference has to have fdo#ABCDE form (where ABCDE is the bug > > number), and has to be at the first line of the commit (it does not > > matter where on that line). > > Sorry, one point is for me not clear: >

Re: [Libreoffice-qa] [ANN] Referencing bugs in commits

2012-02-14 Thread Michael Meeks
On Tue, 2012-02-14 at 20:33 +0400, Ivan Timofeev wrote: > Is it possible somehow include the information about a target version? I guess that -should- be implicit in the branch it is committed to, so - sounds feasible ;-) at least - the expert eye can see that information there already.

Re: [Libreoffice-qa] AOOo Issues [From Symphony]

2012-02-14 Thread Rainer Bielefeld
Cedric Bosdonnat schrieb: Well, we can combine the use of a static list in a wiki page and the greasemonkey script I wrote in the IZ times Hi Cédric, thank you for the hint, unfortunately I don't have skills there and no idea how to use the script. @all: May be someone else can do somethin

Re: [Libreoffice-qa] [ANN] Referencing bugs in commits

2012-02-14 Thread Pierre-André Jacquod
hello, The bug reference has to have fdo#ABCDE form (where ABCDE is the bug number), and has to be at the first line of the commit (it does not matter where on that line). Sorry, one point is for me not clear: by the first line, do you mean "title line" or would it works also as first line o

Re: [Libreoffice-qa] [ANN] Referencing bugs in commits

2012-02-14 Thread Andras Timar
2012/2/14 Ivan Timofeev : > On 14.02.2012 19:31, Michael Meeks wrote: >> >> >> On Tue, 2012-02-14 at 16:16 +0100, Jan Holesovsky wrote: >>> >>> Markus has implemented a nice feature that should help keeping the bugs >>> up to date: whenever you are committing / pushing to git, and you >> >> >>    

Re: [Libreoffice-qa] [ANN] Referencing bugs in commits

2012-02-14 Thread Ivan Timofeev
On 14.02.2012 19:31, Michael Meeks wrote: On Tue, 2012-02-14 at 16:16 +0100, Jan Holesovsky wrote: Markus has implemented a nice feature that should help keeping the bugs up to date: whenever you are committing / pushing to git, and you ooh ! really lovely :-) Great work Mark

Re: [Libreoffice-qa] [ANN] Referencing bugs in commits

2012-02-14 Thread Michael Meeks
On Tue, 2012-02-14 at 16:16 +0100, Jan Holesovsky wrote: > Markus has implemented a nice feature that should help keeping the bugs > up to date: whenever you are committing / pushing to git, and you ooh ! really lovely :-) Great work Markus ! Michael. -- michae

[Libreoffice-qa] [ANN] Referencing bugs in commits

2012-02-14 Thread Jan Holesovsky
Hi, Markus has implemented a nice feature that should help keeping the bugs up to date: whenever you are committing / pushing to git, and you reference the bugs.freedesktop.org bug in the commit message, it will automatically appear as a comment in the bug :-) The bug reference has to have fdo#AB

Re: [Libreoffice-qa] AOOo Issues [From Symphony]

2012-02-14 Thread Christian Lohmaier
Hi Florian, On Tue, Feb 14, 2012 at 2:50 PM, Florian Reisinger wrote: > Why do not use a Metabug like: > https://bugs.freedesktop.org/show_bug.cgi?id=6 > There is a: "See Also:     Add Bug URLs: " and comments... > IMHO that would be much easier... This won't get you newly filed ones, and al

Re: [Libreoffice-qa] AOOo Issues [From Symphony]

2012-02-14 Thread Florian Reisinger
Hi @ll ! Why do not use a Metabug like: https://bugs.freedesktop.org/show_bug.cgi?id=6 There is a: "See Also: Add Bug URLs: " and comments... IMHO that would be much easier... -- Tschüss! | Bye! Florian Reisinger LibO 3.5rc3 Windows 7 SP1 64-bit __

Re: [Libreoffice-qa] AOOo Issues [From Symphony]

2012-02-14 Thread Christian Lohmaier
Hi Rainer, *, On Tue, Feb 14, 2012 at 12:04 PM, Rainer Bielefeld wrote: > Christian Lohmaier schrieb: > >> In the wiki you could use the easy-hacks method, i.e. use a query and >> add it to the page using the feed tag.. > > great tool, unfortunatly I do not have experince at all. how will it > re

Re: [Libreoffice-qa] AOOo Issues [From Symphony]

2012-02-14 Thread Rainer Bielefeld
Christian Lohmaier schrieb: In the wiki you could use the easy-hacks method, i.e. use a query and add it to the page using the feed tag.. Hi, great tool, unfortunatly I do not have experince at all. how will it recognize ÁOoo Issues that have been reviewed by LibO QA? I would have to add e

Re: [Libreoffice-qa] AOOo Issues [From Symphony]

2012-02-14 Thread Christian Lohmaier
Hi Rainer, *, On Tue, Feb 14, 2012 at 9:48 AM, Rainer Bielefeld wrote: >> Hmm - any other way here, without having to pollute a foreign >> bugtracker with LibO-specifics? A static list in the wiki maybe? > > I deal with your concerns, a consequent addition of bug numbers, so that I > can adapt th

Re: [Libreoffice-qa] AOOo Issues [From Symphony]

2012-02-14 Thread Cedric Bosdonnat
Hi Thorsten, Rainer, On Tue, 2012-02-14 at 09:39 +0100, Thorsten Behrens wrote: > > Leave a comment in AOOo bug concerning your result: > > "LibO also affected" > > "LibO not affected" > > If you use exactly those strings we can avoid double work easily > > with a clever query, oyu find it on my W

Re: [Libreoffice-qa] AOOo Issues [From Symphony]

2012-02-14 Thread Rainer Bielefeld
Thorsten Behrens schrieb: Hmm - any other way here, without having to pollute a foreign bugtracker with LibO-specifics? A static list in the wiki maybe? Hi, I deal with your concerns, a consequent addition of bug numbers, so that I can adapt the query link (or the reviewer can add new AOOo n

Re: [Libreoffice-qa] AOOo Issues [From Symphony]

2012-02-14 Thread Thorsten Behrens
Hi Rainer, you wrote: > That's a fruitfully source, we should check that systematically. > absolutely - just did for the presentation bugs, those which I could test (one had a non-public bug document) are fixed for LibO. > Leave a comment in AOOo bug concerning your result: > "LibO also affecte

[Libreoffice-qa] AOOo Issues [From Symphony]

2012-02-14 Thread Rainer Bielefeld
Hi all, Hi Markus, in AOOo Bugzilla I find lots of bugs with [From Symphony] in Subject line, I just took to That's a fruitfully source, we should check that systematically. I recomme