Closed
Bug 1156928
Opened 10 years ago
Closed 9 years ago
Upgrade zamboni to django 1.8.x
Categories
(Marketplace Graveyard :: Code Quality, defect, P1)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: mat, Unassigned)
References
Details
As the title says. With luck, we should be able to remove jingo when switching to 1.8.x.
Cool features we could use include:
- https://docs.djangoproject.com/en/1.8/ref/models/fields/#django.db.models.UUIDField
- https://docs.djangoproject.com/en/1.8/topics/testing/tools/#django.test.TestCase.setUpTestData (which we already have because we cherry picked that)
- https://docs.djangoproject.com/en/1.8/ref/models/instances/#django.db.models.Model.from_db
- Improvements to custom lookups https://docs.djangoproject.com/en/1.8/howto/custom-lookups/ that could help replace some of the magic in translations code
- https://docs.djangoproject.com/en/1.8/ref/models/instances/#django.db.models.Model.refresh_from_db to replace our .reload()
- https://docs.djangoproject.com/en/1.8/ref/django-admin/#django-admin-option---keepdb
And more, including lots of cleanups that should improve quality : https://docs.djangoproject.com/en/1.8/releases/1.8/
Worth nothing that this is a LTS release.
Updated•10 years ago
|
Priority: -- → P4
Updated•10 years ago
|
Severity: normal → enhancement
Updated•9 years ago
|
Whiteboard: [ktlo]
Comment 1•9 years ago
|
||
The end of mainstream support for 1.7.x was April 2015.
The end of extended support for 1.7.x is December 2015.
We should probably get the 1.8.x upgrade on our radar since in 4 months it will no longer be supported.
1.8.x is a long-term support release and will be good at least until April 2018.
Priority: P4 → P3
Comment 2•9 years ago
|
||
This makes me so sad. 1.7, you didn't even get 6 months.
Updated•9 years ago
|
Priority: P3 → P2
Updated•9 years ago
|
Severity: enhancement → major
Updated•9 years ago
|
Priority: P2 → P1
Updated•9 years ago
|
Whiteboard: [ktlo]
Comment 3•9 years ago
|
||
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•