Re: [Libreoffice-qa] Online update testing

2012-08-30 Thread Petr Mladek
klaus-jürgen weghorn ol píše v St 29. 08. 2012 v 23:09 +0200:
 Hi,
 Am 26.08.2012 09:21, schrieb klaus-jürgen weghorn ol:
  Hi Jan,
  Am 16.08.2012 15:53, schrieb Jan Holesovsky:
  Hi Klaus-Juergen, all,
 
  I'd like to ask you test the online update a bit.  I had to do some
  larger changes in order to be able to update the 3.5 line to 3.5.6, so
  now it explicitly preselects 3.5.6 for you, when you try to update from
  an older version.
 
  The 3.6 update (from the previous RC's, for example) should lead you to
  the generic download page.
 
  The 3.6.1.1 doesn't lead to 3.6.1.2.
  LibreOffice 3.6 ist auf dem neuesten Stand.
 
 I want to remember:
 There is no update call from version 3.6.1.1 to official 3.6.1.

It should be fixed now. Please test and report if it does not work.

Best Regards,
Petr

___
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-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://lists.freedesktop.org/archives/libreoffice-qa/

Re: [Libreoffice-qa] Long Time Unconfirmed bugs

2012-08-30 Thread Rainer Bielefeld

Florian Reisinger schrieb:


a) Go to the ML libreoffice-qa-pract...@libreoffice.org
b) If we have some people there, we could from time to time add this
list some bugs of  query [1]
c) Like here, questions could be raised (It could be compared like this:



Hi Florian,

to be honest, I am not happy with the idea of adding more proceedings, 
mailing lists, ... . My suspect is that all that brings up a lot of 
visible activity without adequate progress. We should not invest so much 
time in managing unresolved problems, simply let us use the time to 
solve the problems.


The good part of the idea is to contribute queries like you did in your 
mail. It is something similar like the HardHacks what help us to 
concentrate on old Bugs what should not be forgotten. If we get such a 
priority topic from time to time (every 4 weeks or so) we have something 
where we can see progress with our work Today I see 285 Bugs in your 
query, may be we can reduce that number to 140 until End of September? I 
just started with closing Bug 42403 - SLIDESHOW: linked SVG graphics do 
not show in Slide Show.


Best regards

Rainer
___
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-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://lists.freedesktop.org/archives/libreoffice-qa/


Re: [Libreoffice-qa] Proposed HARDHACK

2012-08-30 Thread Bjoern Michaelsen
On Thu, Aug 30, 2012 at 11:52:38AM +0200, Roman Eisele wrote:
 * https://bugs.freedesktop.org/show_bug.cgi?id=47368
 * https://bugs.freedesktop.org/show_bug.cgi?id=39007
 * https://bugs.freedesktop.org/show_bug.cgi?id=44664

The report only shows 3.6 MAB, it should be easy to extend to 3.5 and 3.7 MABs, 
too.

Best,

Bjoern
___
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-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://lists.freedesktop.org/archives/libreoffice-qa/


Re: [Libreoffice-qa] Long Time Unconfirmed bugs

2012-08-30 Thread Bjoern Michaelsen
Hi,

On Thu, Aug 30, 2012 at 12:26:55PM +0200, Rainer Bielefeld wrote:
 to be honest, I am not happy with the idea of adding more
 proceedings, mailing lists, ... . My suspect is that all that brings
 up a lot of visible activity without adequate progress. We should
 not invest so much time in managing unresolved problems, simply let
 us use the time to solve the problems.

I have to agree with Rainer -- we shouldnt fragment the QA teams communication
channels -- unless this QA list is drowning in traffic and scaring away 
newcomers,
which is not the case yet.

Best,

Bjoern
___
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-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://lists.freedesktop.org/archives/libreoffice-qa/


Re: [Libreoffice-qa] Proposed HARDHACK

2012-08-30 Thread Joel Madero

On 08/29/2012 10:38 PM, Rainer Bielefeld wrote:

Joel Madero schrieb:


We should come up with a better method of tracking vs. each of us making
our own list.


Hi Joel,

yes, indeed!


If everyone wants, they can email me and I will keep a
combined list that we can discuss during our conference call. You can
just email me directly Proposed HARDHACK,


I would prefer a more public collection. I will (today) start another 
thread here where everybody can do a proposal for Bug Numbers, Queries 
filtering candidates or similar, so that everybody can observe the 
collection process and do his own thoughts. But it would be really 
great if you could collect the proposals few days before the next call 
(then we stop the collection, later proposals will be for the next 
call) so that we have a common and clear base for discussion and 
decision.


BTW: I still wonder whether it would be possible to have a LibO 
spreadsheet on a server what can be edited by all interested people 
(here for the collection of data), see [tdf-discuss] Open document 
from server


Best regards

Rainer


Hi Rainer,

I asked for the website team to look into this for the bug triaging 
process as well -- google docs is messy..-- as of yet they haven't 
responded so I'm thinking it's not easy. Google docs IS working for the 
triaging project it's just not ideal. It's a possibility until we find 
something better for HARDHACKS.


Another less than ideal solution is setting a whiteboard status of 
PROPOSEDHARDHACK, then we in the QA team can query these out a couple 
nights before the conference call and write our own thoughts down. I 
actually think I prefer google docs as we already have too many 
whiteboard status'. Ultimately, our own spreadsheet on our own server 
would be ideal.



Best Regards,
Joel
___
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-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://lists.freedesktop.org/archives/libreoffice-qa/


[Libreoffice-qa] ANNOUNCE: Release plan updated - two weeks between RCs

2012-08-30 Thread Petr Mladek
Hi,

on the recent ESC call, we agreed to try two weeks between RCs. It will
allow QA to do more testing. Also it will allow developers to fix the
found regressions.

Please, find the updated release plan at
http://wiki.documentfoundation.org/ReleasePlan


Best Regards,
Petr


PS: We should add more time between 3.7.0 release and 3.7.1-rc1. There
are several possibilities. Let's discuss it as replay to this mail on
the dev and qa mailing lists.

___
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-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://lists.freedesktop.org/archives/libreoffice-qa/


[Libreoffice-qa] Shift 3.7.0 or 3.7.X releases - was: ANNOUNCE: Release plan updated - two weeks between RCs

2012-08-30 Thread Petr Mladek
Petr Mladek píše v Čt 30. 08. 2012 v 16:53 +0200:
 Hi,
 
 on the recent ESC call, we agreed to try two weeks between RCs. It will
 allow QA to do more testing. Also it will allow developers to fix the
 found regressions.
 
 Please, find the updated release plan at
 http://wiki.documentfoundation.org/ReleasePlan

As mentioned, the 3.7.0 release and 3.7.1-rc1 are planed for the same
week now. It is bad because there is no time to proceed feedback from
3.7.0 users.

Possible solutions:

1. Make 3.7.0 two weeks earlier. I am not happy to change this so close
   to the feature freeze.

2. Make 3.7.X bugfix releases 1 or 2 weeks later. It might cause
   troubles for Ubuntu, Fedora, and other distros who planed to use .3
   bugfix release in their distro releases.

   Well, they might use 3.7.3-rc1 or 3.7.2. They should be pretty good
   as well. The number of weeks for bugfixing stays the same.


3. Remove 3.7.0-rc3 or some beta. It would mean to do the hard code
   freeze 1 or two weeks earlier = less time for testing and fixing

4. Do 3.7.0-RCs every week (use the original schedule). There is not
   enough time for feedback = demotivating for QA.


I think that the 2nd solution is the best compromise for 3.7.0. The 1st
variant would be best for the further releases (3.8.0, 3.9.0).

Bjorn, Caolan, others, would you mind if we delay 3.7.X bugfix releases
by 1 or 2 weeks?


Best Regards,
Petr

___
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-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://lists.freedesktop.org/archives/libreoffice-qa/

Re: [Libreoffice-qa] HardHacks

2012-08-30 Thread Bjoern Michaelsen
Hi,

On Sat, Aug 25, 2012 at 08:31:21AM +0200, Rainer Bielefeld wrote:
 ID  OS  Component - Summary
 
 38913   Linux   Libreoffice - CRASH when loading Danish dictionary at
 startup citing msvcr90.dll after upgrade
 https://bugs.freedesktop.org/show_bug.cgi?id=38913

Discussed on ESC and found unsuitable to be picked up by development as-is.

The current bugstate has been summarized in:

 https://bugs.freedesktop.org/show_bug.cgi?id=38913#c41

and explains what is missing for this to be picked up by development. This
hopefully answers the (justified) question from comment 8 in that bug.

Affected reporters are asked to complete the bug, so development can pick it
up.

Also note that during the discussion on the ESC it became clear that such a
summary of the bug history is essential for HardHacks that are longrunning (10
comments). Thus QA volunteers can help out to provide such summaries for
HardHack candidates.

Best,

Bjoern
___
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-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://lists.freedesktop.org/archives/libreoffice-qa/


[Libreoffice-qa] QA Easyhack prosposal

2012-08-30 Thread Florian Reisinger
Hi!

Here I have another idea how to let QA part of the community. I am
going to try to bring this into a simplenods file... What do you
think?


MacOS: 
https://bugs.freedesktop.org/buglist.cgi?type1-0-0=notsubstringorder=Importancelist_id=118326field0-0-0=days_elapsedop_sys=Mac%20OS%20X%20%28All%29chfieldto=Nowchfield=componentchfield=everconfirmedchfield=rep_platformchfield=op_syschfield=prioritychfield=productchfield=qa_contactchfield=reporter_accessiblequery_format=advancedvalue1-0-0=enhancementbug_status=UNCONFIRMEDtype0-0-0=greaterthanvalue0-0-0=30field1-0-0=bug_severityproduct=LibreOffice

Linux: 
https://bugs.freedesktop.org/buglist.cgi?type1-0-0=notsubstringlist_id=118327field0-0-0=days_elapsedop_sys=Linux%20%28All%29chfieldto=Nowquery_format=advancedchfield=componentchfield=everconfirmedchfield=rep_platformchfield=op_syschfield=prioritychfield=productchfield=qa_contactchfield=reporter_accessiblebug_status=UNCONFIRMEDvalue1-0-0=enhancementtype0-0-0=greaterthanvalue0-0-0=100field1-0-0=bug_severityproduct=LibreOffice

Windows: 
https://bugs.freedesktop.org/buglist.cgi?type1-0-0=notsubstringlist_id=118329field0-0-0=days_elapsedop_sys=Windows%20%28All%29chfieldto=Nowquery_format=advancedchfield=componentchfield=everconfirmedchfield=rep_platformchfield=op_syschfield=prioritychfield=productchfield=qa_contactchfield=reporter_accessiblebug_status=UNCONFIRMEDvalue1-0-0=enhancementtype0-0-0=greaterthanvalue0-0-0=100field1-0-0=bug_severityproduct=LibreOffice


All: 
https://bugs.freedesktop.org/buglist.cgi?type1-0-0=notsubstringlist_id=118332field0-0-0=days_elapsedop_sys=Allchfieldto=Nowquery_format=advancedchfield=componentchfield=everconfirmedchfield=rep_platformchfield=op_syschfield=prioritychfield=productchfield=qa_contactchfield=reporter_accessiblebug_status=UNCONFIRMEDvalue1-0-0=enhancementtype0-0-0=greaterthanvalue0-0-0=150field1-0-0=bug_severityproduct=LibreOffice


All (unusual OS) :
https://bugs.freedesktop.org/buglist.cgi?order=Importancelist_id=118334field0-0-0=days_elapsedbug_severity=blockerbug_severity=criticalbug_severity=majorbug_severity=normalbug_severity=minorbug_severity=trivialop_sys=FreeBSDop_sys=NetBSDop_sys=OpenBSDop_sys=BSD%20%28Others%29op_sys=Solarisop_sys=Cygwinop_sys=AIXop_sys=HP-UXop_sys=IRIXop_sys=Interixop_sys=otherchfieldto=Nowchfield=componentchfield=everconfirmedchfield=rep_platformchfield=op_syschfield=prioritychfield=productchfield=qa_contactchfield=reporter_accessiblequery_format=advancedbug_status=UNCONFIRMEDtype0-0-0=greaterthanproduct=LibreOffice



__
Florian Reisinger

Von meinem iPad gesendet
Sent via iPad
___
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-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://lists.freedesktop.org/archives/libreoffice-qa/


Re: [Libreoffice-qa] Proposed HARDHACK

2012-08-30 Thread Joel Madero
I just came up with a potential idea! What about making a custom search on
FDO and just share it with each other? I use a couple custom searches right
now, making them is easy, transparent and shared.

Just a thought

Best Regards,
Joel

On Thu, Aug 30, 2012 at 7:05 AM, Joel Madero jmadero@gmail.com wrote:

 On 08/29/2012 10:38 PM, Rainer Bielefeld wrote:

 Joel Madero schrieb:

  We should come up with a better method of tracking vs. each of us making
 our own list.


 Hi Joel,

 yes, indeed!

  If everyone wants, they can email me and I will keep a
 combined list that we can discuss during our conference call. You can
 just email me directly Proposed HARDHACK,


 I would prefer a more public collection. I will (today) start another
 thread here where everybody can do a proposal for Bug Numbers, Queries
 filtering candidates or similar, so that everybody can observe the
 collection process and do his own thoughts. But it would be really great if
 you could collect the proposals few days before the next call (then we stop
 the collection, later proposals will be for the next call) so that we have
 a common and clear base for discussion and decision.

 BTW: I still wonder whether it would be possible to have a LibO
 spreadsheet on a server what can be edited by all interested people (here
 for the collection of data), see [tdf-discuss] Open document from server

 Best regards

 Rainer

  Hi Rainer,

 I asked for the website team to look into this for the bug triaging
 process as well -- google docs is messy..-- as of yet they haven't
 responded so I'm thinking it's not easy. Google docs IS working for the
 triaging project it's just not ideal. It's a possibility until we find
 something better for HARDHACKS.

 Another less than ideal solution is setting a whiteboard status of
 PROPOSEDHARDHACK, then we in the QA team can query these out a couple
 nights before the conference call and write our own thoughts down. I
 actually think I prefer google docs as we already have too many whiteboard
 status'. Ultimately, our own spreadsheet on our own server would be ideal.


 Best Regards,
 Joel

___
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-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://lists.freedesktop.org/archives/libreoffice-qa/

Re: [Libreoffice-qa] Proposed HARDHACK

2012-08-30 Thread Bjoern Michaelsen
On Wed, Aug 29, 2012 at 06:36:40PM -0700, Joel Madero wrote:
 https://bugs.freedesktop.org/show_bug.cgi?id=47283

Looked at it, Indeed a good candidate.

Best,

Bjoern
___
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-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://lists.freedesktop.org/archives/libreoffice-qa/


Re: [Libreoffice-qa] Regression test (Moztrap) test case localization temporary solution.

2012-08-30 Thread Sophie Gautier

Hi Yi Fan,
On 27/08/2012 07:19, Yi Fan Jiang wrote:

Hi Sophie,

Thanks for following this :) I am looking forward to your further input.

  I'll test more in depth Moztrap tomorrow. For information, I was
  unable to login using Chrome but it was ok with Firefox.

How does it look like when failing to login with Chrome?

There is an issue related with CSRF veirication need to follow in current
our Moztrap instance. It happens in both Chrome and Firefox randomly, though
*refreshing* times of the page will get through the annoying message. Please
see:

https://wiki.documentfoundation.org/Moztrap/Moztrap_User_Guide#Registration_and_Login

Did you meet the similar problem or something else?


This was exactly the problem, and even refreshing didn't work on Chrome, 
I was able to register, but that's all. Firefox was ok, showing the 
error once, but after it was ok.


BTW. I have added you in the test manager group so that you can play with
more features :)


Thanks a lot. I've have a computer crash that prevent me for doing 
anything else than trying to recover everything, but now it's ok and I 
will have time to go further during tomorrow and over the week-end.
Again thanks a lot for working on this and sorry for the delay bring to 
all this from my side.


Kind regards
Sophie
___
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-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://lists.freedesktop.org/archives/libreoffice-qa/


Re: [Libreoffice-qa] [libreoffice-accessibility] Adding Accessibility component to Bug Assistant

2012-08-30 Thread Rainer Bielefeld

Ti tengo d'occhio schrieb:


in my opinion it would be great to have a component for accessibility;
it could let developers to better focus on accessibility bugs and, on
the other hand, blind people to know that accessibility is important for
this project and that submitting bug reports of this type is more than
encouraged…


Hi,

the advantage of an Accessibility Component would be that it can 
easily be selected from a pulldown, no typos or other mistakes can 
happen.But a problem is that an Accessibility Component would not 
indicate what developer might be the one who can fix the problem. So it 
always would be replaced during the bug triaging and fixing process.


An other possibility would be a Whiteboard entry, but that only can be 
done after a report in a second step, typos might happen, it is too modest.


So I currently think about a Bug Submission Assistant enhancement. We 
can add a checkbox Accessibility affected, and the Assistant will add 
Accessibility
a) as additional pseudo key word to the Bug Summary line. The advantage 
of this solution is that the key word would be very visible.

or
b) as additional pseudo key word to the whiteboard
or will
c) set Key word Accessibility to the Keyword pane (it should not be a 
problem to get this new key word from FDO). The advantae of this 
solution is that it also eases and unifies handling in Bugzilla itself, 
not only via BSA.


And of course
d) New Component Accessibility
still can be discussed.

My order of preference (descending):
c - a - b - d

Your opinion?

When we have a solution here, we can start to mark and process 
accessibility bugs with increased priority.


Best regards

Rainer

___
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-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://lists.freedesktop.org/archives/libreoffice-qa/