Closed Bug 731209 Opened 12 years ago Closed 10 years ago

Upgrade Django to version 1.5

Categories

(developer.mozilla.org Graveyard :: Code Cleanup, defect, P3)

Product:
developer.mozilla.org Graveyard
Component:
Code Cleanup
Platform:
x86
macOS
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: groovecoder, Unassigned)

References

Details

(Whiteboard: [specification][type:change][specification-comment:5][dev-papercut]) 

When available.
Blocks: 695774
No longer blocks: 695774
Depends on: 695774
Depends on: 731212
Depends on: 731213
Blocks: 731215
Blocks: 731218
Blocks: 698427
Blocks: 756263
Priority: -- → P2
This is a big bug that shouldn't block July launch.
No longer blocks: 756263
Blocks: 756266
Blocks: 782803
Version: Kuma → unspecified
Component: Website → Landing pages
Component: Landing pages → Security
Depends on: 797592
Depends on: 797594
No longer depends on: 695774
Depends on: 805131
Blocks: 789016
No longer blocks: 789016
Summary: upgrade to django 1.4.1 → Upgrade to django 1.4.1
Depends on: 810120
Whiteboard: u=developer c=infrastructure p= → u=developer c=infrastructure p=2
Priority: P2 → P1
No longer blocks: 756266
Priority: P1 → P2
Summary: Upgrade to django 1.4.1 → Upgrade Django to version 1.5 RC2
Whiteboard: u=developer c=infrastructure p=2 → c=Security sp=2
Depends on: 834326
FYI: Django 1.5 RC2 is "coming soon", but where "soon" probably means "within the next two weeks". I'll have some info on that in the planning meeting, along with thoughts on whether we should start out at RC1 instead.
Summary: Upgrade Django to version 1.5 RC2 → Upgrade Django to version 1.5
Just filling out a specification. Not entirely needed for something like this, but might as well be consistent.

What feature should be changed? Please provide the URL of the feature if possible.
==================================================================================
Django should be updated to version 1.5.

What problems would this solve?
===============================
This would resolve some security concerns inherent in running an old version of Django.

Who would use this?
===================
Developers would be most affected by this change. End users should see very few, if any, changes.

What would users see?
=====================
N/A

What would users do? What would happen as a result?
===================================================
N/A

Is there anything else we should know?
======================================
Whiteboard: c=Security sp=2 → [specification][type:change][specification-comment:5]
Whiteboard: [specification][type:change][specification-comment:5] → [specification][type:change][specification-comment:5][selected]
Whiteboard: [specification][type:change][specification-comment:5][selected] → [specification][type:change][specification-comment:5]
Breaking the 1.4 work into bug 851289 so that we can track them independently, and do not forget about 1.5 once 1.4 is done.
Priority: P2 → P3
No longer blocks: 698427
James, have we finished this already?
Flags: needinfo?(jbennett)
David and James confirmed that we have yet to do this.
Flags: needinfo?(jbennett)
Bug 789016 depends on this, which continues to be a big annoyance for me and reduce my level of contribution to MDN.
Whiteboard: [specification][type:change][specification-comment:5] → [specification][type:change][specification-comment:5][dev-papercut]
Component: Security → Code Cleanup
We won't go to 1.5. We'll go to either 1.6 or 1.7 and file a separate bug for that.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WONTFIX
Product: developer.mozilla.org → developer.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.