BMO/RetiringComponents: Difference between revisions

From MozillaWiki
< BMO
Jump to navigation Jump to search
(Note the page is for bmo admins, and point at the more useful page on deleting components.)
 
(6 intermediate revisions by 4 users not shown)
Line 1: Line 1:
{{Note|This page is for bugzilla.mozilla.org administrators. If you want a component removed, please follow the steps in [[Bugmasters/Projects/Bugzilla_Clean_Up|Bugzilla Clean Up]]}}
Products and components aren't deleted from Bugzilla, since the records of their bugs or the work done on them may be useful. Instead, usually they are changed to disable the creation of new bugs in their category. They can also be moved to a "Graveyard" area.
Products and components aren't deleted from Bugzilla, since the records of their bugs or the work done on them may be useful. Instead, usually they are changed to disable the creation of new bugs in their category. They can also be moved to a "Graveyard" area.


Line 5: Line 7:
For a component to be retired from a still-active product: make a new product in the Graveyard classification that matches the still existing product, then ask IT to run move_bugs, and then contrib/reorg-tools/syncmsandversions.pl to autocreate the versions and milestones.  
For a component to be retired from a still-active product: make a new product in the Graveyard classification that matches the still existing product, then ask IT to run move_bugs, and then contrib/reorg-tools/syncmsandversions.pl to autocreate the versions and milestones.  


===How to move components to the "Graveyard" classification in Bugzilla===
==How to move components to the "Graveyard" classification in Bugzilla==


0. Check for open bugs in the component. Resolve them.<br>
=== Preparation ===
1. Create the new product, for example "Boot2Gecko Graveyard" if it doesn't yet exist, and make sure new bugs cannot be filed in the graveyard product.<br>
2. Find out which flags are enabled for the old product/component by going to editflagtypes.cgi and filtering the flag list based on the product/component using the drop down menus.<br>
3. Go to each flag needed to be preserved, and add the new Graveyard product to the inclusion list.<br>
4. Enable the same groups for the new Graveyard product so private bugs remain private.<br>
5. Create the new component under the Graveyard product. Preferably with the same name, description, users, etc.<br>
6. If there are only a few bugs to move from the old to the graveyard, you can use the mass edit form for buglist.cgi and just spam people if necessary. If there are a lot then the movebugs.pl script is the better way to go (no email). <br>
7. If movebugs.pl is needed move to next section (IT) otherwise skip it and go on to the next.
8. move the bug to mozilla.org:Server Ops:Developer Services and ask them to run the scripts below


For the IT person:
# Check for open bugs in the component. Resolve them.
# Create the new product, for example "Boot2Gecko Graveyard" if it doesn't yet exist, and make sure new bugs cannot be filed in the graveyard product.
# Find out which flags are enabled for the old product/component by going to editflagtypes.cgi and filtering the flag list based on the product/component using the drop down menus.
# Go to each flag needed to be preserved, and add the new Graveyard product to the inclusion list.
# Enable the same groups for the new Graveyard product so private bugs remain private.


(This example is for moving Boot2Gecko Gaia:Calculator to Boot2Gecko Graveyard)
=== Moving a small number of bugs (eg. fewer than 10) ===
# Create the new component under the Graveyard product. Preferably with the same name, description, users, etc.
# Use the mass edit form for buglist.cgi (this will generate bugmail)
# Delete the old component.


1. cd to the web root for BMO (cgi files for Bugzilla)<br>
=== Moving a component into the Graveyard ===
2. # perl contrib/reorg-tools/syncmsandversions.pl Boot2Gecko "Boot2Gecko Graveyard"<br>
This is the most common situation, where an entire component needs to be graveyarded and it doesn't exist yet in the graveyard
3. # perl contrib/reorg-tools/movebugs.pl "Boot2Gecko" "Gaia::Calculator" "Boot2Gecko Graveyard" "Gaia::Calculator"<br>
# Create/Move the bug into bugzilla.mozilla.org::infrastructure with the following instructions:
4. Move bug back to bugzilla.mozilla.org product so admin can remove old component.<br>
#* ''This example is for moving Boot2Gecko Gaia:Calculator to Boot2Gecko Graveyard)''
#* cd to the web root for BMO
#* perl contrib/reorg-tools/syncmsandversions.pl Boot2Gecko "Boot2Gecko Graveyard"
#* perl contrib/reorg-tools/movecomponent.pl "Boot2Gecko" "Boot2Gecko Graveyard" "Gaia::Calculator"
# Once completed, the bug can be resolved/fixed


BMO Admin:
=== Moving bugs into a component which already exists in the Graveyard ===
These steps are required to move bugs ''into an existing component''
# Create/Move the bug into bugzilla.mozilla.org::infrastructure with the following instructions:
#* ''This example is for moving Boot2Gecko Gaia:Calculator to Boot2Gecko Graveyard)''
#* cd to the web root for BMO
#* perl contrib/reorg-tools/syncmsandversions.pl Boot2Gecko "Boot2Gecko Graveyard"
#* perl contrib/reorg-tools/movebugs.pl "Boot2Gecko" "Gaia::Calculator" "Boot2Gecko Graveyard" "Gaia::Calculator"
# Once completed, the move the bug back to the "Administration" component
# Delete the old component and mark the bug as resolved/fixed


Delete old component when all bugs have been moved and close out issue.
[[Category:BMO]]

Latest revision as of 01:56, 9 March 2017

Note: This page is for bugzilla.mozilla.org administrators. If you want a component removed, please follow the steps in Bugzilla Clean Up

Products and components aren't deleted from Bugzilla, since the records of their bugs or the work done on them may be useful. Instead, usually they are changed to disable the creation of new bugs in their category. They can also be moved to a "Graveyard" area.

An entire product can be moved to the "Graveyard" classification easily by someone who has the editclassifications permission.

For a component to be retired from a still-active product: make a new product in the Graveyard classification that matches the still existing product, then ask IT to run move_bugs, and then contrib/reorg-tools/syncmsandversions.pl to autocreate the versions and milestones.

How to move components to the "Graveyard" classification in Bugzilla

Preparation

  1. Check for open bugs in the component. Resolve them.
  2. Create the new product, for example "Boot2Gecko Graveyard" if it doesn't yet exist, and make sure new bugs cannot be filed in the graveyard product.
  3. Find out which flags are enabled for the old product/component by going to editflagtypes.cgi and filtering the flag list based on the product/component using the drop down menus.
  4. Go to each flag needed to be preserved, and add the new Graveyard product to the inclusion list.
  5. Enable the same groups for the new Graveyard product so private bugs remain private.

Moving a small number of bugs (eg. fewer than 10)

  1. Create the new component under the Graveyard product. Preferably with the same name, description, users, etc.
  2. Use the mass edit form for buglist.cgi (this will generate bugmail)
  3. Delete the old component.

Moving a component into the Graveyard

This is the most common situation, where an entire component needs to be graveyarded and it doesn't exist yet in the graveyard

  1. Create/Move the bug into bugzilla.mozilla.org::infrastructure with the following instructions:
    • This example is for moving Boot2Gecko Gaia:Calculator to Boot2Gecko Graveyard)
    • cd to the web root for BMO
    • perl contrib/reorg-tools/syncmsandversions.pl Boot2Gecko "Boot2Gecko Graveyard"
    • perl contrib/reorg-tools/movecomponent.pl "Boot2Gecko" "Boot2Gecko Graveyard" "Gaia::Calculator"
  2. Once completed, the bug can be resolved/fixed

Moving bugs into a component which already exists in the Graveyard

These steps are required to move bugs into an existing component

  1. Create/Move the bug into bugzilla.mozilla.org::infrastructure with the following instructions:
    • This example is for moving Boot2Gecko Gaia:Calculator to Boot2Gecko Graveyard)
    • cd to the web root for BMO
    • perl contrib/reorg-tools/syncmsandversions.pl Boot2Gecko "Boot2Gecko Graveyard"
    • perl contrib/reorg-tools/movebugs.pl "Boot2Gecko" "Gaia::Calculator" "Boot2Gecko Graveyard" "Gaia::Calculator"
  2. Once completed, the move the bug back to the "Administration" component
  3. Delete the old component and mark the bug as resolved/fixed