[Libreoffice-qa] Bugzilla Down?
Hi, After it has been running a little bumpy all morning it seems Bugzilla is down now? I get: Internal Server Error The server encountered an internal error or misconfiguration and was unable to complete your request. Please contact the server administrator, sitewrangl...@freedesktop.org and inform them of the time the error occurred, and anything you might have done that may have caused the error. More information about this error may be available in the server error log. 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] Regression test (Moztrap) test case localization temporary solution.
Hi Yifan, On 04/09/2012 04:35, Yifan Jiang wrote: Hi Sophie, Petr, all, Thanks for the discussion and sorry for the late response that I was busy of other works these days :( no problem :) Visually the second one is also my most favorite, so let's start here. In this week, I will arrange time to update the test cases and make their format consistent with the prototype 2. http://vm12.documentfoundation.org/manage/case/99/ ok, thanks a lot. @Sophie, As for the 3.6.3 testing, do you have an estimation when would it be happening? Currently there are only English cases in the database migrated from Litmus. We will still need some time to migrate other language versions before arranging tests. Looking back to Litmus, there are 4 languages version of test cases: en/de/fr/pt-Br, if necessary we could also create Ja section awaiting for input. It will be on week 41, but it's more because I need deadlines than a really fixed date ;) How do you migrate the tests, would I be able to give an hand or is by using some scripts or some magic ? As for the languages, I'll ask on the list for motivated teams and will tell you. As for the l10n related hacking, they need large scope of changes in both frontend and backend. I would plan at least 1 dev month to do all the stuff including: Moztrap UI l10n implementing, test case l10n hacking and the relevant tests before they are good enough to be online. ok, thanks for this estimation, that will help me in my research for funding. 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] Bugzilla Down?
On Tue, Sep 04, 2012 at 08:31:37AM +0200, Rainer Bielefeld wrote: After it has been running a little bumpy all morning it seems Bugzilla is down now? Got the same, seems back up now. -- Lionel ___ 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] Triage Project Update
Hi Joel, Am 04.09.2012 19:18 schrieb Joel Madero: I have done a complete update of the google document, this being said, if you named a sheet to your name, it's gone. Noel pointed out that a lot of the bugs on the sheet were already triaged so I just started from scratch. I'm still hoping the web team can help us move this away from google docs and get it automated a bit but for now, it is what it is. I'm not sure to understand what you want to have automated, could you elaborate just a little bit (or - if you have done so already - point me to the archived mail)? Thanks, Nino ___ 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] Triage Project Update
Am 04.09.2012 21:52 schrieb Joel Madero: Basically it would be really nice to be able to group and assign bugs the way that the document does. I think bugs are much more manageable this way and we've seen a relative spike in QA triaging activity since starting the process this way. Ok, I see: it makes the process a bit more transparent/obvious. And thus is more pleasant and possibly invites more contributors. Not sure if you looked at the document but it's basically manual everything, I looked at it but could not see what is so special with it... I'll try to compare (please comment if you find this inadequate): I download FDO bugs to Calc, group them based on Component, can be done by a bugzilla query then manually copy and paste into groupings of no more than 50. (is this really that important? for crowdsourcing, it might suffice to do coordination by e-mail) It would be incredibly nice to have the list updated automatically based on FDO, group the bugs based on component and then group each of those to a max of 50 bugs per group. if it's a live query, it's current every time you run it If each group of 50 could then be assigned to a user it would be easy for members of QA to get involved with this project and get this back log taken care of. Ok, I don't know how to build such chunks of 50 bugs using a query - but - is it so important? Couldn't we use e.g. time periods (weeks or months) to group the bugs? Then the number would not be constant but who cares? I'm not sure if this is possible or incredibly time consuming (if it is, probably not worth it). I don't know either but wanted to understand what exactly is needed and if it's possible to find (slightly) different solutions which can be implemented more quickly (or are already existing but not thought of) It would be even better if we, as the QA team could do a custom group and then it could assign us bugs based on that. For instance, I'm a QA member and I want to do 20 bugs that are either Writer, Calc or Presentation, and I want the oldest bugs (in terms of those that have been left UNCONFIRMED for the longest period of time). It could then give me the list and allow me to assign myself to the group, and thus prevent other QA members from getting those bugs in their list when they do a custom search. There is a QA Contact field which has not been used extensively (at least according to my recent search). Could it be used for this purpose? (Rainer? Björn?) Sorry I felt like that was a bit of rambling, let me know if you need it clarified, I can hardly understand it myself ;) So let me be a bit of a devil's advocate, aka clarification helper :-) (I've been working in a project as QA helper years ago for several months, they used excel sheets, so I think I understand the need to master the bugs, and to make the processes transparent and obvious. And thus lower the entry barrier for noobs, too btw.) So my present guess would be: - asking for a web tool is ok but - if there's no better tools ATM, let's stay with google docs for the time coming - but let's also try to use bugzilla itself as much as possible - we have also the wiki, but I do not see much advantage of using it compared to a google spreadsheet as it does not support storing/handling structured data. But it's a web, so we can document all processes nicely and link the documents in the wiki. Regards, Nino ___ 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] Triage Project Update
I agree that FDO has some benefits but the limitation is really that each user is needed to query every time, the possibility of overlap is great, and no one is really responsible for an individual bug until the query is made and someone takes the time to look into it. I'm not sure if others would agree but it seems like having a group of 50 or so and being able to just do those at your convenience makes people more likely to help and feel like their is an end in sight for their portion. This is vs. just seeing a never ending list from FDO or even having to teach new users (or even not new users) exactly what to search for every time with FDO. Similar to how developers assign themselves bugs and then can just go look at their own bugs (My Bugs) it would be nice to have this ability for QA triagers but have it somewhat automated since it's just triaging, not programming. In the long run (once we're through the back log of 650+ that are really old), it would be amazing if we had a team of QA staff that signed up to have bugs auto assigned to them for triaging. What I imagine: QA triagers sign up for components they are willing to triage and their max load New bug is reported, if the bug has a component listed the bug gets auto assigned for triaging purposes according to some rule(s) For now the google docs works, FDO does not as it is now but I'll discuss this further with Bjoern, Petr Rainer to see if we can come up with something more functional than the chaos that is FDO :) Or maybe I'm just not familiar enough with FDO to really feel comfortable myself with it, this is more likely than not true :) Best Regards, Joel On 09/04/2012 01:53 PM, Nino Novak wrote: Am 04.09.2012 21:52 schrieb Joel Madero: Basically it would be really nice to be able to group and assign bugs the way that the document does. I think bugs are much more manageable this way and we've seen a relative spike in QA triaging activity since starting the process this way. Ok, I see: it makes the process a bit more transparent/obvious. And thus is more pleasant and possibly invites more contributors. Not sure if you looked at the document but it's basically manual everything, I looked at it but could not see what is so special with it... I'll try to compare (please comment if you find this inadequate): I download FDO bugs to Calc, group them based on Component, can be done by a bugzilla query then manually copy and paste into groupings of no more than 50. (is this really that important? for crowdsourcing, it might suffice to do coordination by e-mail) It would be incredibly nice to have the list updated automatically based on FDO, group the bugs based on component and then group each of those to a max of 50 bugs per group. if it's a live query, it's current every time you run it If each group of 50 could then be assigned to a user it would be easy for members of QA to get involved with this project and get this back log taken care of. Ok, I don't know how to build such chunks of 50 bugs using a query - but - is it so important? Couldn't we use e.g. time periods (weeks or months) to group the bugs? Then the number would not be constant but who cares? I'm not sure if this is possible or incredibly time consuming (if it is, probably not worth it). I don't know either but wanted to understand what exactly is needed and if it's possible to find (slightly) different solutions which can be implemented more quickly (or are already existing but not thought of) It would be even better if we, as the QA team could do a custom group and then it could assign us bugs based on that. For instance, I'm a QA member and I want to do 20 bugs that are either Writer, Calc or Presentation, and I want the oldest bugs (in terms of those that have been left UNCONFIRMED for the longest period of time). It could then give me the list and allow me to assign myself to the group, and thus prevent other QA members from getting those bugs in their list when they do a custom search. There is a QA Contact field which has not been used extensively (at least according to my recent search). Could it be used for this purpose? (Rainer? Björn?) Sorry I felt like that was a bit of rambling, let me know if you need it clarified, I can hardly understand it myself ;) So let me be a bit of a devil's advocate, aka clarification helper :-) (I've been working in a project as QA helper years ago for several months, they used excel sheets, so I think I understand the need to master the bugs, and to make the processes transparent and obvious. And thus lower the entry barrier for noobs, too btw.) So my present guess would be: - asking for a web tool is ok but - if there's no better tools ATM, let's stay with google docs for the time coming - but let's also try to use bugzilla itself as much as possible - we have also the wiki, but I do not see much advantage of using it compared to a google spreadsheet as it
