751340 - [d2c] Devhub: Show developers if their add-on qualifies for D2C

Status: RESOLVED WONTFIX

(addons.mozilla.org Graveyard :: Developer Pages, defect, P4)

Description

[Gregory Koberger (:gkoberger)]

Right now, we don't tell developers if their add-on qualifies for D2C. Most developers probably don't know what D2C is even -- let alone how to ensure their add-ons are automatically upgraded.

So, we're going to make a few changes to the Edit Version page.

Note that this has to be dynamic, since changing minVersion and maxVersion will affect d2c.

Comment 1

[Gregory Koberger (:gkoberger)]

Attachment: mockup

IF IT DOES QUALIFY FOR D2C

If it does qualify for D2C, we'll remove the maxVersion dropdown and instead say "and later (?)". If they mouseover the question mark, we'll show a tooltip that says:

"You don't need to manually update maxVersion for this add-on anymore. All newer versions of Firefox will automatically support your add-on. You can opt out by setting strictCompatibility in your install.rdf."

If the user hits "Change maxVersion", the select should appear inside the modal. If they change the maxVersion but it doesn't affect d2c, we should explain strictCompatibility to them. 

The select is inside the modal because changing the maxVersion can affect d2c status, and it'll get confusing if you can change the maxVersion but it's still d2c compatible. If the changes to maxVersion affect the d2c status, the select show show up outside the modal where it used to be. (Sorry this is complicated, given how it's just an edge case.)

Comment 2

[Gregory Koberger (:gkoberger)]

Attachment: mock

IF IT DOESN'T QUALIFY FOR D2C

If it doesn't, we'll show a yellow warning. A yellow warning may seem a bit harsh, but the goal is to get everyone d2c compatible. When they click Fix It, we'll show a popup that explains why their add-on isn't compatible. Each reason should make it very clear what they have to do to make it d2c. If there are multiple reasons, show them all.