Closed Bug 659371 Opened 14 years ago Closed 13 years ago

Build file attachment backend into Kuma Platform

Categories

(developer.mozilla.org Graveyard :: Wiki pages, defect, P1)

Product:
developer.mozilla.org Graveyard
Component:
Wiki pages
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: openjck, Assigned: jbennett)

References

Details

(Whiteboard: u=user c=wiki s= p=3)

This is a top-level task. It will act as a dependency of more specific features (versioning, etc).
Priority: -- → P1
Blocks: 711477
Whiteboard: u=user c=wiki s=2012-07-03 p=
Assignee: nobody → jbennett
Blocks: 665740, 665747
Blocks: mdn-attachments
No longer blocks: 665747
Changing the dependency tree up a bit. Disregard comment 0.
Summary: Build file attachment features into Kuma Platform → Build file attachment backend into Kuma Platform
Be sure to collect enough data so that the versioning interface (bug 665747) is possible later.
Whiteboard: u=user c=wiki s=2012-07-03 p= → u=user c=wiki s=2012-07-03 p=3
Friendly all aboard ping. We scheduled this one to be completed before the next sprint. How's it looking?
Whiteboard: u=user c=wiki s=2012-07-03 p=3 → u=user c=wiki s=2012-07-13 p=3
Whiteboard: u=user c=wiki s=2012-07-13 p=3 → u=user c=wiki s=2012-07-18 p=3
We've completed file migration... I think this is done?
Those blockers should have been dependencies. What is the status of bug 711477 and bug 766741?
No longer blocks: 711477, mdn-attachments, 665740
Depends on: 711477, mdn-attachments, 665740
Blocks: 711477
No longer depends on: 711477
No longer depends on: mdn-attachments
Blocks: mdn-attachments
No longer blocks: 711477
Blocks: 771763
Whiteboard: u=user c=wiki s=2012-07-18 p=3 → u=user c=wiki s= p=3
I think this is actually done, since :ubernostrum's file attachment models are in place and working.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Component: Website → Landing pages
Product: developer.mozilla.org → developer.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.