Re: [Libreoffice-qa] suggestion for weekly-bug-summary
jmadero wrote and try to figure out how that page is generated. I triedcouldn't find it for the life of me :-/ Hi! It is quite easy - it is implemented as Extension. The page template is extensions/WeeklyBugSummary/template/en/default/pages/weekly-bug-summary.html.tmpl. The code with SQL queries is extensions/WeeklyBugSummary/Extension.pm. Best regards. BTW: I would like to see Bugzilla custom changes announcements (with rationale when needed) somewhere else than only in git repo at https://gerrit.libreoffice.org/gitweb?p=bugzilla.git;a=shortlog;h=refs/heads/tdf-4.4.6. -- View this message in context: http://nabble.documentfoundation.org/Libreoffice-qa-suggestion-for-weekly-bug-summary-tp4138113p4138376.html Sent from the QA mailing list archive at Nabble.com. ___ 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] suggestion for weekly-bug-summary
On Sat, Jan 31, 2015 at 3:12 PM, bfoman bfo.bugm...@spamgourmet.com wrote: BTW: I would like to see Bugzilla custom changes announcements (with rationale when needed) somewhere else than only in git repo at https://gerrit.libreoffice.org/gitweb?p=bugzilla.git;a=shortlog;h=refs/heads/tdf-4.4.6. Yep, sounds good to me! Just need to find enough hours in the day :P Would be neat for us to have blog posts/tweets about some of our bigger improvements. Best, --R -- Robinson Tryon QA Engineer - The Document Foundation LibreOffice Community Outreach Herald qu...@libreoffice.org ___ 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] suggestion for weekly-bug-summary
Top posting just to say thanks! Best, Joel On 01/31/2015 04:28 AM, Robinson Tryon wrote: On Fri, Jan 30, 2015 at 1:01 AM, Bjoern Michaelsen bjoern.michael...@canonical.com wrote: Nope. Bugzilla is Infra. Infra is on Redmine. Here are the Bugzilla bugs on redmine: https://redmine.documentfoundation.org/projects/infrastructure/issues?utf8=%E2%9C%93set_filter=1f%5B%5D=status_idop%5Bstatus_id%5D=of%5B%5D=category_idop%5Bcategory_id%5D=%3Dv%5Bcategory_id%5D%5B%5D=50f%5B%5D=c%5B%5D=trackerc%5B%5D=statusc%5B%5D=priorityc%5B%5D=subjectc%5B%5D=assigned_toc%5B%5D=updated_onc%5B%5D=due_dategroup_by= Sorry about the ugly urls; I'll see if we can make those look nicer. To file a new bug, use the 'Infrastructure' project and the 'Bugzilla' category. https://redmine.documentfoundation.org/projects/infrastructure/issues/new (I haven't figured out how to pass-in params in that URL to set the category) If infra wants to do a lot of triage and prioritizing over all bugs filed under 'Infra', we can talk about having a separate or sub-project just for Bugzilla and QA tasks. Cheers, --R ___ 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] suggestion for weekly-bug-summary
On 01/31/2015 06:12 AM, bfoman wrote: jmadero wrote and try to figure out how that page is generated. I triedcouldn't find it for the life of me :-/ Hi! It is quite easy - it is implemented as Extension. The page template is extensions/WeeklyBugSummary/template/en/default/pages/weekly-bug-summary.html.tmpl. The code with SQL queries is extensions/WeeklyBugSummary/Extension.pm. Best regards. BTW: I would like to see Bugzilla custom changes announcements (with rationale when needed) somewhere else than only in git repo at https://gerrit.libreoffice.org/gitweb?p=bugzilla.git;a=shortlog;h=refs/heads/tdf-4.4.6. Indeed - quite easy. I wonder why grep wasn't finding anything useful :-/ Anyways, thanks for the link. Maybe before editing it to death we should propose what we'd like to track (with queries) so it's transparent and does not become a place where everyone places their own favorite queries :) Best, 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] Unable to set ux-advise bugs to NEW in new bugzilla
Hi All, As ux-advise bugs are not supposed to be affecting the QA bug count, the new bugzilla doesnt permit me to change its status when creating a bug report. -- Regards, Jay Philips ___ 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] Unable to set ux-advise bugs to NEW in new bugzilla
On Sat, Jan 31, 2015 at 9:58 PM, Jay Philips philip...@hotmail.com wrote: Hi All, As ux-advise bugs are not supposed to be affecting the QA bug count, the new bugzilla doesnt permit me to change its status when creating a bug report. Hi Jay, I did some tweaking of the config in Bugzilla 4.4.6 to make sure that bugs would default to UNCONFIRMED when filed, and the simplest method was to make UNCONFIRMED the only choice for a newly-created bug. You can always create the bug, then change status to NEW afterwards. Or do a bulk-change, if you're filing a bunch of reports at once. From my understanding, the difference I saw on the backend is related to changing bug workflows that have been introduced to Bugzilla in modern versions. We can try to bring back the ability to set bugs to NEW during filing, but I think it's worth our time to also take a look at the suggested workflow in Bugzilla, and see if we might wish to adopt it. Best, --R -- Robinson Tryon QA Engineer - The Document Foundation LibreOffice Community Outreach Herald qu...@libreoffice.org ___ 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] suggestion for weekly-bug-summary
On Fri, Jan 30, 2015 at 4:15 PM, Joel Madero jmadero@gmail.com wrote: I agree that it would be good it is possible. Can I change add a query myself to that page? So you can clone our instance of bugzilla: git clone git://gerrit.libreoffice.org/bugzilla and try to figure out how that page is generated. I triedcouldn't find it for the life of me :-/ Anyone can check out the tdf-bugzilla repo. I think that I might need to set up some code review via gerrit for patches, but I've been kept busy with Bugzilla and other QA tasks in the last couple weeks -- guess I'll file a task for myself in Redmine to get gerrit working :-) For the time being, if you've already submitted a contrib statement as a LibreOffice developer, feel free to send me patches via email and I'll review and merge them in. If stuff isn't MPL, or you didn't write it, then we'll need to discuss further. Deployment is via salt and git, and I have some notes here: https://wiki.documentfoundation.org/QA/Bugzilla/Deployment https://wiki.documentfoundation.org/QA/Bugzilla/Development But as Bjoern said, we'd have to license it appropriately and possibly upstream. AFAIK there's no legal requirement to upstream our patches to Bugzilla, but we're definitely in favor of it! (Especially as it reduces the size of the patchset we have to migrate from one Bugzilla release to the next) Best, --R -- Robinson Tryon QA Engineer - The Document Foundation LibreOffice Community Outreach Herald qu...@libreoffice.org ___ 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] suggestion for weekly-bug-summary
On Fri, Jan 30, 2015 at 1:52 AM, Bjoern Michaelsen bjoern.michael...@canonical.com wrote: On Thu, Jan 29, 2015 at 04:14:24PM -0800, Joel Madero wrote: I've never been a fan of this split to begin with. Having a much less visible means of suggesting enhancement requests or bugs pretty much just sucks. Just speaking for myself, I'm very unlikely to report any enhancement requests about bugzilla on redmine... Oh, hate the split too. The split will not go away easily though (I tried. Hard.). Yeah, sucks. Still, the best we can do now is have a clear cut rather than fractured border between the two. It's indeed frustrating to go through the work of the Bugzilla migration, only to run into the challenges presented by a split bugtracker. Two bugtrackers may not be ideal, but there are some concrete steps we can take to reduce the pain: * Set up LDAP to allow shared logins for both trackers * Decide on protocol for dealing with bugs misfiled in the wrong tracker * Make sure that QA and other groups feel welcomed to file bugs and enhancements in redmine, particularly against Bugzilla So we're only tracking enhancement requests if the reporter can either (1) do it themselves; or (2) they can show that it's reasonably resourced? I can't imagine a similar strategy working for LibreOffice itself - we might as well close 99% of enhancement requests. I don't get why we'd have two different philosophies just because one is infra and the other is something else? IMHO, just because we're mandated to use a different tool shouldn't change our policies regarding what's valid. Others with bigger hats can always override me, but at least for enhancement suggestions regarding Bugzilla, I'd suggest that we use the same threshold as we use for bugs filed in Bugzilla. So, maybe Im overcautious. ;) As an exaggeration: There is a risk that we end up with 20 people working on making our Bugzilla nice and beautiful and 1 guy working on triaging LibreOffice. Also note that all customization cumulates to create extra pains during updates etc. IMHO we should just keep in mind to keep the fixed costs of running our Bugzilla constant and rather low[1]. Sure, there are definitely trade-offs to be had. All of the QA Team work that will take place in Redmine will be meta-work, and I expect those tasks will appeal to only a subset of our total members. The entire goal of the meta work will be simplifying and improving the effectiveness of QA, so if we end up with a 20:1 ratio of people improving Bugzilla vs. Triaging, either we'll end up with the best improvements to any Bugzilla, anywhere, or we'll run out of tasks in a week! Now that we've upgraded Bugzilla to a much more modern version, we can also take a look at our current bug workflow and compare that to the suggested workflow from Bugzilla itself. It's possible that we might want to adopt some of the new changes from upstream. [1] For example that we ended up with a Redmine/Bugzilla split (which is already a simplification over the mess we had before that) is ultimately a result of bit too much fast-and-loose play with extending, creating and customizing services. Lesson learned: It's always good to try to plan for the future, and to involve other TDF/LibreOffice teams when making decisions that impact them. Cheers, --R -- Robinson Tryon QA Engineer - The Document Foundation LibreOffice Community Outreach Herald qu...@libreoffice.org ___ 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] suggestion for weekly-bug-summary
On Fri, Jan 30, 2015 at 1:01 AM, Bjoern Michaelsen bjoern.michael...@canonical.com wrote: Nope. Bugzilla is Infra. Infra is on Redmine. Here are the Bugzilla bugs on redmine: https://redmine.documentfoundation.org/projects/infrastructure/issues?utf8=%E2%9C%93set_filter=1f%5B%5D=status_idop%5Bstatus_id%5D=of%5B%5D=category_idop%5Bcategory_id%5D=%3Dv%5Bcategory_id%5D%5B%5D=50f%5B%5D=c%5B%5D=trackerc%5B%5D=statusc%5B%5D=priorityc%5B%5D=subjectc%5B%5D=assigned_toc%5B%5D=updated_onc%5B%5D=due_dategroup_by= Sorry about the ugly urls; I'll see if we can make those look nicer. To file a new bug, use the 'Infrastructure' project and the 'Bugzilla' category. https://redmine.documentfoundation.org/projects/infrastructure/issues/new (I haven't figured out how to pass-in params in that URL to set the category) If infra wants to do a lot of triage and prioritizing over all bugs filed under 'Infra', we can talk about having a separate or sub-project just for Bugzilla and QA tasks. Cheers, --R -- Robinson Tryon QA Engineer - The Document Foundation LibreOffice Community Outreach Herald qu...@libreoffice.org ___ 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/
