Reconfiguring for clarity (




13 years ago
8 years ago


(Reporter: morgamic, Assigned: justdave)


Firefox Tracking Flags

(Not tracked)




13 years ago
We need help restructuring Bugzilla for Mozilla Update.  There are a number of changes we need:

a) Rename Product from "Update" -> "" -- is this possible?

b) Rename Components:
* Web Site -> Public Pages
* Developers -> Developer Pages
* Plugin Listings -> Plugins
* Listings -> Search

c) Add Components:
** Maintenance Scripts
** Search Plugins
** Policy

d) Add Target Milestones:
* 2.2, 2.3, 2.4, 2.5, 2.6, 2.7, 2.8, 2.9, 3.0

We need this ASAP to help organize the mess of bugs we have, and assign TM's that correspond to dates (we'd list those dates somewhere else in case they'd change).

Also, "Update" and a lot of the components were vague and/or confusing so we're just trying to get organized.

If some of these changes are not possible for whatever reason, I apologize.  Seems like they should be doable thoug.  Lastly, thanks -- we appreciate the help.  :)

Comment 1

13 years ago
(In reply to comment #0)
> We need help restructuring Bugzilla for Mozilla Update.  There are a number of
> changes we need:
> * Listings -> Search
On second thought -- would it be possible to just delete "Listings"?  Its existence is pointless.  I will move everything over to "Web Site" (to be "Public Pages) since it is basically a subset of that.


Comment 2

13 years ago
renaming products requires working w/ justdave, everything else should be possible.

deleting components requires them to be empty. i'll add the tms now. note that for new components you need to specify descriptions and it's appreciated if you suggest dummy qa contacts and default assignees.

I can empty components, but sometimes it's easier on me if other people take the blame for moves.

Comment 3

13 years ago
I'm already moving things from Listings -> Web Site -- talked to justdave about that, too.

I'll ask justdave about the Product rename.  Thanks timeless.

Comment 4

13 years ago
Adding additional information for Component changes below:

Note: default assignee for all is ""; we track these by watching the QA.

(In reply to comment #0)
> b) Rename Components:
> * Web Site -> Public Pages
No change aside from renaming.

> * Developers -> Developer Pages
No change aside from renaming.

> * Plugin Listings -> Plugins
Change description:
For problems with or changes to Plugin listings, the Plugin Finder Service, or anything relating to Plugins on <a href=""></a>.  Plugins are third-party binaries like Flash, Quicktime, Java, etc.

> c) Add Components:
> ** Maintenance Scripts
For problems or changes to regularly scheduled maintenance scripts that update and clean data.


> ** Search Plugins
Problems or changes for Search Plugins hosted on, or their public-facing web pages.  Search Plugins are .src files that let users add custom search engines to their search bar (upper right).


> ** Policy
Problems or questions about policies.  Also for reporting obvious violations of Mozilla or policies related to an add-on or group of add-ons.


Comment 5

13 years ago
Note that there is a url field available for "URL describing milestones for this product", it's currently blank, would you like to specify a url?

Also, currently the --- line for milestones is before 2.0, if you want to move it to somewhere else (e.g. after 2.1) please let me know.

You now have 2.2..3.0.

I've renamed Developer Pages, Plugins, and Public Pages.

As I don't have the ability to setup recycled accounts, you'll have to wait for marcia to do that.
Ok, so to close this one out and to confirm, the following need to still be created - I can do these three.

c) Add Components:
** Maintenance Scripts
** Search Plugins
** Policy

I will create the QA contacts requested as well. The other open items are deleting Listings (justdave) and the product rename.
Ok, my part is done - QA contacts and new components created. Over to justdave for his piece to get this one off my plate.
Assignee: marcia → justdave
marcia: Can you do s/@update/@add-ons/ as per the #bmo discussion, please? :)

Comment 9

13 years ago
Dave, instead of deleting Listings could you rename it:
New name: Add-ons
QA: add-ons@add-ons.bugs
Description: For reporting problems with a specific add-on page or its data.

After more discussion, we all realized there wasn't a good place for add-on-specific problems, so Listings can be used for that, and the rename is easier than the delete.

So -- things left to do:
# Listings rename
# Update ->

Thanks to all of you for your help! Everything else looks great. :)

Comment 10

13 years ago
The description for Maintenance Scripts is wrong (copy and paste strikes again!)
Severity: normal → major
OS: Mac OS X 10.3 → All
Priority: -- → P1
Hardware: Macintosh → All

Comment 11

13 years ago
Timeless/marcia: ping

Can we get some traction here please? The renaming of listings, qa contact change and description change don't need a sysadmin, and us add-ons people would much appreciate it!

Changing the description for Maintenance scripts would also be great :)

The renaming of the product isn't so urgent.
Everything in Comment 9 has been completed. 
Last Resolved: 13 years ago
Resolution: --- → FIXED
Addons product rename requires back-end changes because of our custom product-chooser template.
Resolution: FIXED → ---
ok, done.
Last Resolved: 13 years ago13 years ago
Resolution: --- → FIXED

Comment 15

12 years ago
some later bug appears to have removed some of the milestones, but otherwise everything was done.
Component: Bugzilla: Keywords & Components → Administration
Product: →
You need to log in before you can comment on or make changes to this bug.