Re: [Libreoffice-qa] daily MAB summary and CCing of MABs (was: MAB/Priority and Severity)
On Mon, Jun 29, 2015 at 11:57:10AM +0200, Eike Rathke wrote: What exactly do you mean with review here? I don't think we should spend too much time on that during the ESC call, but I'd be ok with some does anyone see a bug on this list that shouldn't belong there topic. Yes, the latter is actually pretty much what I had in mind for the ESC 'review'. Best, Bjoern ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice-qa] daily MAB summary and CCing of MABs (was: MAB/Priority and Severity)
On Mon, Jun 29, 2015 at 11:57:10AM +0200, Eike Rathke wrote: What exactly do you mean with review here? I don't think we should spend too much time on that during the ESC call, but I'd be ok with some does anyone see a bug on this list that shouldn't belong there topic. Yes, the latter is actually pretty much what I had in mind for the ESC 'review'. 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] daily MAB summary and CCing of MABs (was: MAB/Priority and Severity)
Hi Bjoern, On Monday, 2015-06-29 11:28:02 +0200, Bjoern Michaelsen wrote: - create a query that show all priority: highest bugs that have been touched in the last 25 hours (daily), 8 days (weekly)[1] - have a bot send these summaries daily or weekly to the dev-list - drop the MABs are CC'ed to the dev-list Personally, I would go with 'daily summaries', just like for gerrit. Note that even with that, it will reduce the spammage of the dev-list to 1 daily mail that is actually read, instead of ~4 that are likely ignored. This would mean that we would have: - a daily summary of MAB/priority highest activity to the dev-list - no additional spammage of the dev-list Sounds all good to me, though I think every other day would be sufficient. Plus, have a named query for that (and possibly others) so one can quickly generate a fresh list whenever needed. - weekly review of bugs that have been newly raised to 'priority:highest' in the ESC call What exactly do you mean with review here? I don't think we should spend too much time on that during the ESC call, but I'd be ok with some does anyone see a bug on this list that shouldn't belong there topic. Eike -- LibreOffice Calc developer. Number formatter stricken i18n transpositionizer. GPG key ID 0x65632D3A - 2265 D7F3 A7B0 95CC 3918 630B 6A6C D5B7 6563 2D3A Better use 64-bit 0x6A6CD5B765632D3A here is why: https://evil32.com/ Care about Free Software, support the FSFE https://fsfe.org/support/?erack pgpWwK7s3B_KF.pgp Description: PGP signature ___ 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: daily MAB summary and CCing of MABs (was: [Libreoffice-qa] MAB/Priority and Severity)
Hi Bjoern, On Monday, 2015-06-29 11:28:02 +0200, Bjoern Michaelsen wrote: - create a query that show all priority: highest bugs that have been touched in the last 25 hours (daily), 8 days (weekly)[1] - have a bot send these summaries daily or weekly to the dev-list - drop the MABs are CC'ed to the dev-list Personally, I would go with 'daily summaries', just like for gerrit. Note that even with that, it will reduce the spammage of the dev-list to 1 daily mail that is actually read, instead of ~4 that are likely ignored. This would mean that we would have: - a daily summary of MAB/priority highest activity to the dev-list - no additional spammage of the dev-list Sounds all good to me, though I think every other day would be sufficient. Plus, have a named query for that (and possibly others) so one can quickly generate a fresh list whenever needed. - weekly review of bugs that have been newly raised to 'priority:highest' in the ESC call What exactly do you mean with review here? I don't think we should spend too much time on that during the ESC call, but I'd be ok with some does anyone see a bug on this list that shouldn't belong there topic. Eike -- LibreOffice Calc developer. Number formatter stricken i18n transpositionizer. GPG key ID 0x65632D3A - 2265 D7F3 A7B0 95CC 3918 630B 6A6C D5B7 6563 2D3A Better use 64-bit 0x6A6CD5B765632D3A here is why: https://evil32.com/ Care about Free Software, support the FSFE https://fsfe.org/support/?erack pgphtBiljgUCv.pgp Description: PGP signature ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
daily MAB summary and CCing of MABs (was: [Libreoffice-qa] MAB/Priority and Severity)
Hi, On Tue, Jun 23, 2015 at 09:32:06PM +0200, Bjoern Michaelsen wrote: This is for the ESC to both be aware of newly marked important bugs -- and also to weed out one or another wrongly marked high priority bug. Also, this should help us keep the total number of high priority bugs both under control and on the radar. Along with this: Once MABs are just priority: highest I wonder if it makes sense to: - create a query that show all priority: highest bugs that have been touched in the last 25 hours (daily), 8 days (weekly)[1] - have a bot send these summaries daily or weekly to the dev-list - drop the MABs are CC'ed to the dev-list Personally, I would go with 'daily summaries', just like for gerrit. Note that even with that, it will reduce the spammage of the dev-list to 1 daily mail that is actually read, instead of ~4 that are likely ignored. This would mean that we would have: - a daily summary of MAB/priority highest activity to the dev-list - no additional spammage of the dev-list - weekly review of bugs that have been newly raised to 'priority:highest' in the ESC call Feedback welcome. If there is no objection here and on the ESC, I would write an EasyHack for it then. Best, Bjoern [1] Like: daily (currently 4 items): https://bugs.documentfoundation.org/buglist.cgi?bug_status=UNCONFIRMEDbug_status=NEWbug_status=ASSIGNEDbug_status=REOPENEDbug_status=RESOLVEDbug_status=VERIFIEDbug_status=CLOSEDbug_status=NEEDINFObug_status=PLEASETESTchfieldfrom=-25hchfieldto=Nowcolumnlist=component%2Cassigned_to%2Cshort_desc%2Cchangeddate%2Clongdescs.count%2Cbug_severity%2Cstatus_whiteboardlist_id=545979priority=highestproduct=LibreOfficequery_based_on=query_format=advancedresolution=--- weekly (currently 21 items): https://bugs.documentfoundation.org/buglist.cgi?bug_status=UNCONFIRMEDbug_status=NEWbug_status=ASSIGNEDbug_status=REOPENEDbug_status=RESOLVEDbug_status=VERIFIEDbug_status=CLOSEDbug_status=NEEDINFObug_status=PLEASETESTchfieldfrom=-8dchfieldto=Nowcolumnlist=component%2Cassigned_to%2Cshort_desc%2Cchangeddate%2Clongdescs.count%2Cbug_severity%2Cstatus_whiteboardlist_id=545982priority=highestproduct=LibreOfficequery_format=advancedresolution=--- ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice-qa] MAB/Priority and Severity
On Tue, Jun 23, 2015 at 3:51 PM, Joel Madero jmadero@gmail.com wrote: On 06/23/2015 12:32 PM, Bjoern Michaelsen wrote: Hi, On Sun, May 31, 2015 at 01:14:54PM -0700, Joel Madero wrote: So the time has finally arrived that we are moving forward with _locking out priority/severity_. This means that *MAB will be retired*. I'd like to suggest to add this query as a reocurring item for the Robinson and the rest of the call to look at during the QA section of the ESC call: https://bugs.documentfoundation.org/buglist.cgi?bug_status=UNCONFIRMEDbug_status=NEWbug_status=ASSIGNEDbug_status=REOPENEDbug_status=RESOLVEDbug_status=VERIFIEDbug_status=CLOSEDbug_status=NEEDINFObug_status=PLEASETESTchfield=prioritychfieldfrom=-8dchfieldto=Nowchfieldvalue=highestlist_id=545001priority=highestproduct=LibreOfficequery_format=advancedresolution=--- It shows: - open bugs - that were changed to priority highest (thus a MAB) in the last 8 days (aka ~since the last call) - and currently are still priority highest (and thus a MAB) This is for the ESC to both be aware of newly marked important bugs -- and also to weed out one or another wrongly marked high priority bug. Also, this should help us keep the total number of high priority bugs both under control and on the radar. @Robinson: Can you take that up? Sure, I'll take a look at that. Along with this - I created the patch months ago that is sitting in the test instance to block priority/severity from being changed by non-contributors. Beluga and I put in some time adding all devs and QA members (or at least the vast majority) to a new group in bugzilla so that they will have the rights without requesting. At this point I'm just waiting for Robinson to give me some feedback as to what the hold up is. I'm happy to deploy the changes to production asap -- perhaps tomorrow after the ESC call would work well. I just want to make sure that I have some QA folks available to hammer on the changes and make sure nothing wonky has happened. I don't think that we'll see any interference between the patches and the git-integration for the devs, but that'll be another piece to double-check. Cheers, --R -- Robinson Tryon QA Engineer - The Document Foundation LibreOffice Community Outreach Herald qu...@libreoffice.org 802-379-9482 | IRC: colonelqubit on Freenode ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice-qa] MAB/Priority and Severity
Hi, On Sun, May 31, 2015 at 01:14:54PM -0700, Joel Madero wrote: So the time has finally arrived that we are moving forward with _locking out priority/severity_. This means that *MAB will be retired*. I'd like to suggest to add this query as a reocurring item for the Robinson and the rest of the call to look at during the QA section of the ESC call: https://bugs.documentfoundation.org/buglist.cgi?bug_status=UNCONFIRMEDbug_status=NEWbug_status=ASSIGNEDbug_status=REOPENEDbug_status=RESOLVEDbug_status=VERIFIEDbug_status=CLOSEDbug_status=NEEDINFObug_status=PLEASETESTchfield=prioritychfieldfrom=-8dchfieldto=Nowchfieldvalue=highestlist_id=545001priority=highestproduct=LibreOfficequery_format=advancedresolution=--- It shows: - open bugs - that were changed to priority highest (thus a MAB) in the last 8 days (aka ~since the last call) - and currently are still priority highest (and thus a MAB) This is for the ESC to both be aware of newly marked important bugs -- and also to weed out one or another wrongly marked high priority bug. Also, this should help us keep the total number of high priority bugs both under control and on the radar. @Robinson: Can you take that up? Best, Bjoern ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice-qa] MAB/Priority and Severity
Hi, On Sun, May 31, 2015 at 01:14:54PM -0700, Joel Madero wrote: So the time has finally arrived that we are moving forward with _locking out priority/severity_. This means that *MAB will be retired*. I'd like to suggest to add this query as a reocurring item for the Robinson and the rest of the call to look at during the QA section of the ESC call: https://bugs.documentfoundation.org/buglist.cgi?bug_status=UNCONFIRMEDbug_status=NEWbug_status=ASSIGNEDbug_status=REOPENEDbug_status=RESOLVEDbug_status=VERIFIEDbug_status=CLOSEDbug_status=NEEDINFObug_status=PLEASETESTchfield=prioritychfieldfrom=-8dchfieldto=Nowchfieldvalue=highestlist_id=545001priority=highestproduct=LibreOfficequery_format=advancedresolution=--- It shows: - open bugs - that were changed to priority highest (thus a MAB) in the last 8 days (aka ~since the last call) - and currently are still priority highest (and thus a MAB) This is for the ESC to both be aware of newly marked important bugs -- and also to weed out one or another wrongly marked high priority bug. Also, this should help us keep the total number of high priority bugs both under control and on the radar. @Robinson: Can you take that up? 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] MAB/Priority and Severity
On 06/23/2015 12:32 PM, Bjoern Michaelsen wrote: Hi, On Sun, May 31, 2015 at 01:14:54PM -0700, Joel Madero wrote: So the time has finally arrived that we are moving forward with _locking out priority/severity_. This means that *MAB will be retired*. I'd like to suggest to add this query as a reocurring item for the Robinson and the rest of the call to look at during the QA section of the ESC call: https://bugs.documentfoundation.org/buglist.cgi?bug_status=UNCONFIRMEDbug_status=NEWbug_status=ASSIGNEDbug_status=REOPENEDbug_status=RESOLVEDbug_status=VERIFIEDbug_status=CLOSEDbug_status=NEEDINFObug_status=PLEASETESTchfield=prioritychfieldfrom=-8dchfieldto=Nowchfieldvalue=highestlist_id=545001priority=highestproduct=LibreOfficequery_format=advancedresolution=--- It shows: - open bugs - that were changed to priority highest (thus a MAB) in the last 8 days (aka ~since the last call) - and currently are still priority highest (and thus a MAB) This is for the ESC to both be aware of newly marked important bugs -- and also to weed out one or another wrongly marked high priority bug. Also, this should help us keep the total number of high priority bugs both under control and on the radar. @Robinson: Can you take that up? Along with this - I created the patch months ago that is sitting in the test instance to block priority/severity from being changed by non-contributors. Beluga and I put in some time adding all devs and QA members (or at least the vast majority) to a new group in bugzilla so that they will have the rights without requesting. At this point I'm just waiting for Robinson to give me some feedback as to what the hold up is. @Robinson - if texting is easier than IRC or email - feel free to text me with suggestions for times that we can push this change once and for all. I have 3 more that I intend on making but I want to wait until this one is done before doing more. 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/
Re: [Libreoffice-qa] MAB/Priority and Severity
On 06/23/2015 12:32 PM, Bjoern Michaelsen wrote: Hi, On Sun, May 31, 2015 at 01:14:54PM -0700, Joel Madero wrote: So the time has finally arrived that we are moving forward with _locking out priority/severity_. This means that *MAB will be retired*. I'd like to suggest to add this query as a reocurring item for the Robinson and the rest of the call to look at during the QA section of the ESC call: https://bugs.documentfoundation.org/buglist.cgi?bug_status=UNCONFIRMEDbug_status=NEWbug_status=ASSIGNEDbug_status=REOPENEDbug_status=RESOLVEDbug_status=VERIFIEDbug_status=CLOSEDbug_status=NEEDINFObug_status=PLEASETESTchfield=prioritychfieldfrom=-8dchfieldto=Nowchfieldvalue=highestlist_id=545001priority=highestproduct=LibreOfficequery_format=advancedresolution=--- It shows: - open bugs - that were changed to priority highest (thus a MAB) in the last 8 days (aka ~since the last call) - and currently are still priority highest (and thus a MAB) This is for the ESC to both be aware of newly marked important bugs -- and also to weed out one or another wrongly marked high priority bug. Also, this should help us keep the total number of high priority bugs both under control and on the radar. @Robinson: Can you take that up? Along with this - I created the patch months ago that is sitting in the test instance to block priority/severity from being changed by non-contributors. Beluga and I put in some time adding all devs and QA members (or at least the vast majority) to a new group in bugzilla so that they will have the rights without requesting. At this point I'm just waiting for Robinson to give me some feedback as to what the hold up is. @Robinson - if texting is easier than IRC or email - feel free to text me with suggestions for times that we can push this change once and for all. I have 3 more that I intend on making but I want to wait until this one is done before doing more. Best, Joel ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: MAB/Priority and Severity
On Sun, 31 May 2015 22:14:54 +0200, Joel Madero jmadero@gmail.com wrote: Hi All! So the time has finally arrived that we are moving forward with _locking out priority/severity_. This means that *MAB will be retired*. I will miss MABs... expecially the fact there were different list for the different codelines (is. mab4.3, mab4.4 and mab5.0) that was very useful for user to decide wheter to stick on the stable branch or move to the fresh branch just reading the list of the specific issues of each branch so is there any plan to generate a query about the new highest priority bugs which can separate all these issues in a fashion similar to current MABs lists? ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
MAB/Priority and Severity
Hi All! So the time has finally arrived that we are moving forward with _locking out priority/severity_. This means that *MAB will be retired*. What this mean: 1) If you notice that you lack privileges then just email me and I'll add you to the list (add your bugzilla email account)[1][2] 2) *MAB will be _equivalent_ to _highest_* (so anything that you previously would have thrown on MAB list should be set to highest); 3) Severity should be according to the flowchart https://wiki.documentfoundation.org/images/0/06/Prioritizing_Bugs_Flowchart.jpg; 4) Because users will be locked out it is incredibly important to explain to them why we set the importance/severity the way we did - leave a nice comment ;) *Important: *If there are _any_ issues with this plan, you've got about a week to shoot us an email so that we can work out any kinks. This was in the making for the past 2 years and we're finally there. Best, Joel [1] Robinson and myself will be combing through commiters and triagers to try to add as many people as possible to contributor list as possible without having to personally request access - if you notice that you do not have privileges and want them you can email anyone with admin privileges from bugzilla, if you want these privileges you can request them. Without requesting contributor privileges you will be prevented from changing severity/priority - all triagers/devs should have these privileges. [2] If you're interested in getting admin privileges please shoot me an email asking for those and we can discuss it - for those of you who have been really active in QA land, I encourage you to request the privileges so that you can help maintain the bug tracker :) ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
[Libreoffice-qa] MAB/Priority and Severity
Hi All! So the time has finally arrived that we are moving forward with _locking out priority/severity_. This means that *MAB will be retired*. What this mean: 1) If you notice that you lack privileges then just email me and I'll add you to the list (add your bugzilla email account)[1][2] 2) *MAB will be _equivalent_ to _highest_* (so anything that you previously would have thrown on MAB list should be set to highest); 3) Severity should be according to the flowchart https://wiki.documentfoundation.org/images/0/06/Prioritizing_Bugs_Flowchart.jpg; 4) Because users will be locked out it is incredibly important to explain to them why we set the importance/severity the way we did - leave a nice comment ;) *Important: *If there are _any_ issues with this plan, you've got about a week to shoot us an email so that we can work out any kinks. This was in the making for the past 2 years and we're finally there. Best, Joel [1] Robinson and myself will be combing through commiters and triagers to try to add as many people as possible to contributor list as possible without having to personally request access - if you notice that you do not have privileges and want them you can email anyone with admin privileges from bugzilla, if you want these privileges you can request them. Without requesting contributor privileges you will be prevented from changing severity/priority - all triagers/devs should have these privileges. [2] If you're interested in getting admin privileges please shoot me an email asking for those and we can discuss it - for those of you who have been really active in QA land, I encourage you to request the privileges so that you can help maintain the bug tracker :) ___ 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: MAB/Priority and Severity
Hi, Maybe after update the flowchart, the link could go beside Importance selection. So an easy access is given for everybody. Miguel Ángel. -- View this message in context: http://nabble.documentfoundation.org/MAB-Priority-and-Severity-tp4150125p4150135.html Sent from the Dev mailing list archive at Nabble.com. ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
