Reclassify all existing add-ons into new categories (CAT-2)

VERIFIED FIXED in 3.4

Status

VERIFIED FIXED
11 years ago
3 years ago

People

(Reporter: baz, Assigned: baz)

Tracking

Dependency tree / graph

Details

(URL)

(Assignee)

Description

11 years ago
As specified in the AMO v3.2 PRD (Update:RequirementsV32)
(Assignee)

Comment 1

11 years ago
We were able to do this via the AMO admin interface without requiring code changes. So this is mostly done. The only exception is the "Interface Customizations" category which Madhava and I believe should be subsumed under the new "Themes & Appearance Category", so that's why I'm leaving this open for now. 
(Assignee)

Updated

11 years ago
Assignee: nobody → basil
When we've decided and made the changes, please don't forget to email dev-l10n-web@lists.m.o and let them know about the updates.

Comment 3

11 years ago
Adding two bugs that should be fixed by this.
Blocks: 372852, 379144
(Assignee)

Comment 4

11 years ago
Can't do much with this until the new categories page is live.
Depends on: 396737
(Assignee)

Comment 5

11 years ago
Doesn't depend on resolution anymore
No longer blocks: 372852
Does depend on resolution.
Wil, can you find the old migration stuff and apply that here?  If not please pick this up and write the migration SQL.
Assignee: basil → clouserw
(Assignee)

Comment 8

11 years ago
Category mapping is here - http://wiki.mozilla.org/Update:RequirementsV32
It looks like this has been done already for Firefox but not any of the other applications.  Basil, can you do what you did for Firefox for the rest of the applications?  Also, were the localizers notified when the categories were changed so they could update the localizations?

Switching all the extensions (type:1) in the "Interface Customizations" category into themes (type:2) is a bit of work.  For one thing, a theme can't be in any of the extension categories, so any add-ons in "Interface Customizations" will be removed from any other categories it's in.  If you want to do this I can start working on SQL, but I want to verify that's the road we want to go down.
(Assignee)

Comment 10

11 years ago
Wil,

1) I can take a crack at the other apps.
2) I have not reached out to any localizers for the string changes, I was assuming that this would be part of the list that the web L10N team would have to deal with for AMO v3.2
3) I'm not asking for a type switch. So, what needs to happen is to have a script/SQL that migrates from Interface Customizations as a category to "Themes & Appearance" as a category. I can do that in the admin UI right now but that would be confusing since then we'll have two references to themes. We are eliminating themes (type:2) as a top level category and merging them into Themes & Appearances. Does that make sense?
Assignee: clouserw → basil
(Assignee)

Updated

11 years ago
Target Milestone: 3.2 → 3.4
(Assignee)

Comment 11

11 years ago
OK, we can finally close this. We've moved away from having themes be in hybrid pages and they are back on their own. Also, a bunch of work was done to clean up the former interface customizations category, now known as Appearance.
Status: NEW → RESOLVED
Last Resolved: 11 years ago
Resolution: --- → FIXED
Verified FIXED -- this has been done for some time now :-)
Status: RESOLVED → VERIFIED
Product: addons.mozilla.org → addons.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.