Making bulk changes to bugs.koha-community.org; bug emails will be turned off briefly
Everyone, As I mentioned in my previous thread about updating Bugzilla to better make use of the Status field, I'll be taking bug emails offline for a period of time while I make bulk changes to the statuses. This is to prevent everyone from being horribly spammed. I will reactivate the emails once the changes are complete. I'll try to be on IRC for the duration of this maintenance job, in case anyone has any emergency questions. Cheers, -Ian -- Ian Walls Lead Development Specialist ByWater Solutions ALA Midwinter Booth #2048 Phone # (888) 900-8944 http://bywatersolutions.com ian.walls@bywatersolutions.com Twitter: @sekjal
Bulk changes are complete. Bug emails have been turned back on. Hopefully no one's inbox has been flooded. Summary of changes: - Moved 'patch status' values into their new corresponding Status values - Note that "patch pushed" is mapped to "Pushed to Master" now - Created two new statuses: - In Discussion: for things with deeper ramifications that we need to discuss as a community before committing to the codebase - Pushed to Stable: a status to be used by the Release Maintainer to indicate that a patch is now in the stable release. Workflow should follow this from after "Pushed to Master" - Created patch status workflows to match, well, our workflow. You can't set a bug report directly to Passed QA unless it's been Signed Off, etc. - Obsoleted 'patch status' and it's dependency on Importance Work remaining to be done: - Shared reports need to be updated. Since I'm not the creator of these, I cannot edit them for everyone else. Most of the key ones are owed by either Paul P. or Chris C. - New reports for other statuses, like "In Discussion", "Pushed to Stable" or "Does not apply" - Updating community and personal documentation to reflect the new change in patch submission paperwork. I'm hoping that we'll now be able to auto-set the Status with git-bz, for example, which will streamline our process as developers. - Updating bugs that have already been pushed to stable from the defauled "Pushed to Master" value (or, better yet, they could be closed... hint hint) - Restoring lost Importance data on Needs Signoff, Signed Off, Passed QA and other statuses. There is a history link for changes to a bug report, available in the right column above the "see also" and "change sponsored?" fields, but doing this cleanup will likely need to be manual. Please let me know if any other complications have arisen because of this change. Discussion of additional fields to add can be put into separate threads, for easy readability. Cheers, -Ian On Sat, Jan 14, 2012 at 7:52 PM, Ian Walls <ian.walls@bywatersolutions.com>wrote:
Everyone,
As I mentioned in my previous thread about updating Bugzilla to better make use of the Status field, I'll be taking bug emails offline for a period of time while I make bulk changes to the statuses. This is to prevent everyone from being horribly spammed. I will reactivate the emails once the changes are complete.
I'll try to be on IRC for the duration of this maintenance job, in case anyone has any emergency questions.
Cheers,
-Ian
-- Ian Walls Lead Development Specialist ByWater Solutions ALA Midwinter Booth #2048 Phone # (888) 900-8944 http://bywatersolutions.com ian.walls@bywatersolutions.com Twitter: @sekjal
-- Ian Walls Lead Development Specialist ByWater Solutions ALA Midwinter Booth #2048 Phone # (888) 900-8944 http://bywatersolutions.com ian.walls@bywatersolutions.com Twitter: @sekjal
* Ian Walls (ian.walls@bywatersolutions.com) wrote:
Bulk changes are complete.A Bug emails have been turned back on.A Hopefully no one's inbox has been flooded.
Work remaining to be done: * Shared reports need to be updated.A Since I'm not the creator of these, I cannot edit them for everyone else.A Most of the key ones are owed by either Paul P. or Chris C.
I have updated the existing ones, new ones still need to be made for any not in the footer now Chris -- Chris Cormack Catalyst IT Ltd. +64 4 803 2238 PO Box 11-053, Manners St, Wellington 6142, New Zealand
Who has the permissions to change the "My bugs" search? Bugs with the new statuses do not appear in the "My bugs" saved search. Regards, Jared 2012/1/14 Chris Cormack <chrisc@catalyst.net.nz>
* Ian Walls (ian.walls@bywatersolutions.com) wrote:
Bulk changes are complete.A Bug emails have been turned back on.A Hopefully no one's inbox has been flooded.
Work remaining to be done: * Shared reports need to be updated.A Since I'm not the creator of these, I cannot edit them for everyone else.A Most of the key ones are owed by either Paul P. or Chris C.
I have updated the existing ones, new ones still need to be made for any not in the footer now
Chris
-- Chris Cormack Catalyst IT Ltd. +64 4 803 2238 PO Box 11-053, Manners St, Wellington 6142, New Zealand
_______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
-- Jared Camins-Esakov Bibliographer, C & P Bibliography Services, LLC (phone) +1 (917) 727-3445 (e-mail) jcamins@cpbibliography.com (web) http://www.cpbibliography.com/
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Le 15/01/2012 02:46, Chris Cormack a écrit :
* Ian Walls (ian.walls@bywatersolutions.com) wrote:
Bulk changes are complete.A Bug emails have been turned back on.A Hopefully no one's inbox has been flooded.
Work remaining to be done: * Shared reports need to be updated.A Since I'm not the creator of these, I cannot edit them for everyone else.A Most of the key ones are owed by either Paul P. or Chris C.
I have updated the existing ones, new ones still need to be made for any not in the footer now Chris, the passed QA one still has "priority=patch sent" in it, could you fix it ? You also haven't updated at all the "no status" query. I suspect it can be removed.
- -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : (33) 4 91 81 35 08 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJPFClEAAoJEK81SonuhyGo7TQIAL6jyyBr9pCfzkkP+elphiyV 9uMh26r3MIDgssooEv4C/uIj1907W7MW7ujQCZgox7CeBpjsx6Bvo3H86HFZBF05 RCDZMUJTKIrLCkRvOUE0TygBc//HSrF/js49T7X8XHRtH11qVlIJxzCuhU60Og4B GA7UHhobC3C0rZExqPnU3m/sbHjj76nuTLehKoJf9KaibmMW7CKGIrKwA9ZVKKYU TZmEVrBITUcm9c5hBfENnikfxNHu+22E8dFvTAshNkatPgByLXboCKRiThmkcTg1 uw8ww3KwM5i6SRFX5qPd+/uUYoAvt0hEu3JRDwkhJPrZdqMw8LGNSHVVosdIUO0= =f1rH -----END PGP SIGNATURE-----
Same for No status.. -----Oorspronkelijk bericht----- Van: koha-devel-bounces@lists.koha-community.org [mailto:koha-devel-bounces@lists.koha-community.org] Namens Paul Poulain Verzonden: maandag 16 januari 2012 14:42 Aan: koha-devel@lists.koha-community.org Onderwerp: Re: [Koha-devel] Making bulk changes to bugs.koha-community.org; bug emails will be turned off briefly -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Le 15/01/2012 02:46, Chris Cormack a écrit :
* Ian Walls (ian.walls@bywatersolutions.com) wrote:
Bulk changes are complete.A Bug emails have been turned back on.A Hopefully no one's inbox has been flooded.
Work remaining to be done: * Shared reports need to be updated.A Since I'm not the creator of these, I cannot edit them for everyone else.A Most of the key ones are owed by either Paul P. or Chris C.
I have updated the existing ones, new ones still need to be made for any not in the footer now Chris, the passed QA one still has "priority=patch sent" in it, could you fix it ? You also haven't updated at all the "no status" query. I suspect it can be removed.
- -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : (33) 4 91 81 35 08 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJPFClEAAoJEK81SonuhyGo7TQIAL6jyyBr9pCfzkkP+elphiyV 9uMh26r3MIDgssooEv4C/uIj1907W7MW7ujQCZgox7CeBpjsx6Bvo3H86HFZBF05 RCDZMUJTKIrLCkRvOUE0TygBc//HSrF/js49T7X8XHRtH11qVlIJxzCuhU60Og4B GA7UHhobC3C0rZExqPnU3m/sbHjj76nuTLehKoJf9KaibmMW7CKGIrKwA9ZVKKYU TZmEVrBITUcm9c5hBfENnikfxNHu+22E8dFvTAshNkatPgByLXboCKRiThmkcTg1 uw8ww3KwM5i6SRFX5qPd+/uUYoAvt0hEu3JRDwkhJPrZdqMw8LGNSHVVosdIUO0= =f1rH -----END PGP SIGNATURE----- _______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
On 17 January 2012 02:42, Paul Poulain <paul.poulain@biblibre.com> wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Le 15/01/2012 02:46, Chris Cormack a écrit :
* Ian Walls (ian.walls@bywatersolutions.com) wrote:
Bulk changes are complete.A Bug emails have been turned back on.A Hopefully no one's inbox has been flooded.
Work remaining to be done: * Shared reports need to be updated.A Since I'm not the creator of these, I cannot edit them for everyone else.A Most of the key ones are owed by either Paul P. or Chris C.
I have updated the existing ones, new ones still need to be made for any not in the footer now Chris, the passed QA one still has "priority=patch sent" in it, could you fix it ? You also haven't updated at all the "no status" query. I suspect it can be removed.
Done to both Chris
First, thanks for making the changes. About: Created patch status workflows to match our workflow: Could you add Passed QA to the statuses listed at Needs signoff? Sometimes the QA team can do this in one time. Similarly, ASSIGNED could be handy at Needs signoff as well as at Signed off. Changed: Since all reports changed, we lost the last change date (which I [mis]used heavily..) Would it be possible to add a column on Bugzilla for the date associated with the last attachment ? I think it would be very useful for bug wranglers and QAers. This field is displayed now under each attachment in the Attachments block. What did you think of "Needs additional signoff" by the way? Marcel ________________________________ Van: koha-devel-bounces@lists.koha-community.org [koha-devel-bounces@lists.koha-community.org] namens Ian Walls [ian.walls@bywatersolutions.com] Verzonden: zondag 15 januari 2012 2:28 To: koha-devel@lists.koha-community.org Onderwerp: Re: [Koha-devel] Making bulk changes to bugs.koha-community.org; bug emails will be turned off briefly Bulk changes are complete. Bug emails have been turned back on. Hopefully no one's inbox has been flooded. Summary of changes: * Moved 'patch status' values into their new corresponding Status values * Note that "patch pushed" is mapped to "Pushed to Master" now * Created two new statuses: * In Discussion: for things with deeper ramifications that we need to discuss as a community before committing to the codebase * Pushed to Stable: a status to be used by the Release Maintainer to indicate that a patch is now in the stable release. Workflow should follow this from after "Pushed to Master" * Created patch status workflows to match, well, our workflow. You can't set a bug report directly to Passed QA unless it's been Signed Off, etc. * Obsoleted 'patch status' and it's dependency on Importance Work remaining to be done: * Shared reports need to be updated. Since I'm not the creator of these, I cannot edit them for everyone else. Most of the key ones are owed by either Paul P. or Chris C. * New reports for other statuses, like "In Discussion", "Pushed to Stable" or "Does not apply" * Updating community and personal documentation to reflect the new change in patch submission paperwork. I'm hoping that we'll now be able to auto-set the Status with git-bz, for example, which will streamline our process as developers. * Updating bugs that have already been pushed to stable from the defauled "Pushed to Master" value (or, better yet, they could be closed... hint hint) * Restoring lost Importance data on Needs Signoff, Signed Off, Passed QA and other statuses. There is a history link for changes to a bug report, available in the right column above the "see also" and "change sponsored?" fields, but doing this cleanup will likely need to be manual. Please let me know if any other complications have arisen because of this change. Discussion of additional fields to add can be put into separate threads, for easy readability. Cheers, -Ian On Sat, Jan 14, 2012 at 7:52 PM, Ian Walls <ian.walls@bywatersolutions.com<mailto:ian.walls@bywatersolutions.com>> wrote: Everyone, As I mentioned in my previous thread about updating Bugzilla to better make use of the Status field, I'll be taking bug emails offline for a period of time while I make bulk changes to the statuses. This is to prevent everyone from being horribly spammed. I will reactivate the emails once the changes are complete. I'll try to be on IRC for the duration of this maintenance job, in case anyone has any emergency questions. Cheers, -Ian -- Ian Walls Lead Development Specialist ByWater Solutions ALA Midwinter Booth #2048 Phone # (888) 900-8944<tel:%28888%29%20900-8944> http://bywatersolutions.com ian.walls@bywatersolutions.com<mailto:ian.walls@bywatersolutions.com> Twitter: @sekjal -- Ian Walls Lead Development Specialist ByWater Solutions ALA Midwinter Booth #2048 Phone # (888) 900-8944 http://bywatersolutions.com ian.walls@bywatersolutions.com<mailto:ian.walls@bywatersolutions.com> Twitter: @sekjal
Le 15/01/2012 02:28, Ian Walls a écrit :
o Pushed to Stable: a status to be used by the Release Maintainer to indicate that a patch is now in the stable release. Workflow should follow this from after "Pushed to Master"
For more complete information: * when I push, i'll set "Pushed to master". If the patch does not have to be pushed to 3.6, (ie: an ENH for 3.8), i'll set version to rel_3_8. If the RMaint should deal with it, i'll set version to rel_3_6 (if it's not already the case) Reminder: rel_3_8 version is, for instance, used only by me. If you've something to say against master, then set version=master. (when 3.8 will be released though, everyone will be encouraged to use rel_3_8, of course)
* Obsoleted 'patch status' and it's dependency on Importance (it's not importance, it's priority)
So, if you want something to be on top of our list, you can set Priority to 1. I often recieve pm from ppl asking for QA or pushing of bug XXXX. Please don't use pm now, but priority !!! I'll use it too to set a low priority on what i'll investigate on the bottom of my pile. Note that I also use the last modification date as a sorter, to avoid having a bug staying "forever" in the bottom of the pile. low priority does not mean that I don't care !!! (and I hope it's the same thing for others !)
* Shared reports need to be updated. Since I'm not the creator of these, I cannot edit them for everyone else. Most of the key ones are owed by either Paul P. or Chris C. done for those i'm the author of.
* New reports for other statuses, like "In Discussion", done "Pushed to Stable" or "Does not apply" I think it's something that is for the RMaint mainly. I haven't made it myself. -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : (33) 4 91 81 35 08
participants (6)
-
Chris Cormack -
Chris Cormack -
Ian Walls -
Jared Camins-Esakov -
Marcel de Rooy -
Paul Poulain