BMO/RetiringComponents: Difference between revisions

Jump to navigation Jump to search

BMO/RetiringComponents (view source)

Revision as of 14:26, 19 August 2014

59 bytes added ,  19 August 2014
no edit summary
No edit summary
Line 5: Line 5:
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.<br>
8. move the bug to "mozilla.org :: Server Operations :Developer Services" and ask them to run the scripts below. <br>


# 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.


'''For the IT person:'''
=== 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.


(This example is for moving Boot2Gecko Gaia:Calculator to Boot2Gecko Graveyard)
=== 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
# 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"
# Once completed, the bug can be resolved/fixed


1. cd to the web root for BMO<br>
=== Moving bugs into a component which already exists in the Graveyard ===
2. perl contrib/reorg-tools/syncmsandversions.pl Boot2Gecko "Boot2Gecko Graveyard"<br>
These steps are required to move bugs ``into an existing component``
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 the 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
Note: movecomponent.pl only works when the the component name will stay the same. Some of the requests we get are to move bugs between different products and differing component names. For those we have to use movebugs.pl.  If the request to retire a component to a graveyard product, the component doesn't exist yet, and the component name will stay the same, then use movecomponent.pl instead of movebugs.pl.
#* perl contrib/reorg-tools/syncmsandversions.pl Boot2Gecko "Boot2Gecko Graveyard"
 
#* perl contrib/reorg-tools/movecomponent.pl "Boot2Gecko" "Gaia::Calculator" "Boot2Gecko Graveyard" "Gaia::Calculator"
'''BMO Admin:'''
# 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.
Glob
Confirmed users
1,201

edits

Retrieved from "https://wiki.mozilla.org/Special:MobileDiff/1006999"

Navigation menu