BMO/RetiringComponents: Difference between revisions
| Line 15: | Line 15: | ||
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> | 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. | 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 | 8. move the bug to "mozilla.org :: Server Operations :Developer Services" and ask them to run the scripts below | ||
For the IT person: | For the IT person: | ||
| Line 21: | Line 21: | ||
(This example is for moving Boot2Gecko Gaia:Calculator to Boot2Gecko Graveyard) | (This example is for moving Boot2Gecko Gaia:Calculator to Boot2Gecko Graveyard) | ||
1. cd to the web root for BMO | 1. cd to the web root for BMO<br> | ||
2. | 2. perl contrib/reorg-tools/syncmsandversions.pl Boot2Gecko "Boot2Gecko Graveyard"<br> | ||
3. | 3. perl contrib/reorg-tools/movebugs.pl "Boot2Gecko" "Gaia::Calculator" "Boot2Gecko Graveyard" "Gaia::Calculator"<br> | ||
4. Move bug back to bugzilla.mozilla.org product so admin can remove old component.<br> | 4. Move the bug back to bugzilla.mozilla.org product so admin can remove old component.<br> | ||
BMO Admin: | BMO Admin: | ||
Delete old component when all bugs have been moved and close out issue. | Delete old component when all bugs have been moved and close out issue. | ||
Revision as of 05:56, 8 May 2013
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
0. Check for open bugs in the component. Resolve them.
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.
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.
3. Go to each flag needed to be preserved, and add the new Graveyard product to the inclusion list.
4. Enable the same groups for the new Graveyard product so private bugs remain private.
5. Create the new component under the Graveyard product. Preferably with the same name, description, users, etc.
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).
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 Operations :Developer Services" and ask them to run the scripts below
For the IT person:
(This example is for moving Boot2Gecko Gaia:Calculator to Boot2Gecko Graveyard)
1. cd to the web root for BMO
2. perl contrib/reorg-tools/syncmsandversions.pl Boot2Gecko "Boot2Gecko Graveyard"
3. perl contrib/reorg-tools/movebugs.pl "Boot2Gecko" "Gaia::Calculator" "Boot2Gecko Graveyard" "Gaia::Calculator"
4. Move the bug back to bugzilla.mozilla.org product so admin can remove old component.
BMO Admin:
Delete old component when all bugs have been moved and close out issue.