Closed Bug 606280 Opened 15 years ago Closed 15 years ago

New version page

Categories

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

Product:
addons.mozilla.org Graveyard
Component:
Developer Pages
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED FIXED
Milestone:
5.12.6

People

(Reporter: jbalogh, Assigned: potch)

References

Details

Formerly part of bug 599043, but it would be better to get all the dependencies done first. Most of this page is dynamic and driven by js. http://people.mozilla.com/~chowse/drop/amo/devtools/v3/manage_addon/06_versions_add.png More details in bug 599043 comment 0.
No longer depends on: 599043
Depends on: 599043
Assignee: nobody → jbalogh
Target Milestone: 5.12.3 → 5.12.2
Depends on: 599042
Target Milestone: 5.12.2 → 5.12.3
Priority: -- → P1
Blocks: 611224
Blocks: 611202
Depends on: 611355
Blocks: 522386
Whiteboard: [11/15 transfer to potch]
Target Milestone: 5.12.3 → 5.12.4
I'm going to argue with chowse that the "Upload a New Version" page should pop up the new file form and then take you to the version edit page when that succeeds. We extract compat info from the file and you can edit release notes and approval notes on the edit page. This should post to /addon/:id/versions/add with the hash of a file upload, similar to the add-file page.
Assignee: jbalogh → thepotch
Whiteboard: [11/15 transfer to potch]
chowse/jbalogh: can you sort this out? thx
Target Milestone: 5.12.4 → 5.12.5
Assignee: thepotch → chowse
1. Click "Upload a New Version" on /versions 2. Upload your file in the validation/upload modal. 3. On submit, redirect to the new /versions/:id detail page. chowse is ecstatic about the new scheme.
Assignee: chowse → thepotch
Target Milestone: 5.12.5 → 5.12.6
Severity: normal → critical
https://github.com/jbalogh/zamboni/commit/2b053f3c62d1a5
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Product: addons.mozilla.org → addons.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.