845593 - Upgrade Mozillians to Django 1.5.x

Status: VERIFIED FIXED

(Participation Infrastructure :: Phonebook, defect)

Description

[Justin Crawford [:hoosteeno] [:jcrawford]]

Relnotes: https://docs.djangoproject.com/en/1.5/releases/1.5/
PyPI: https://pypi.python.org/pypi/Django/1.5
https://docs.djangoproject.com/en/1.5/internals/deprecation/

Let's wait until it's had some time to ripen, but we'll probably want to do this in Q2/Q3.

Comment 1

[Giorgos Logiotatidis [:giorgos]]

Agree. We should keep up with new releases of django and other libraries we use by following playdoh updates. That should be fixed with bugs 805180 and 759482.

Comment 2

[Dan Poirier [:dpoirier]]

Now 1.6 is out...

Comment 3

[Dan Poirier [:dpoirier]]

Django 1.5 and later have support for custom user models. That would enable us to combine the current User and UserProfile models into one, which would greatly simplify code in a lot of places.

Comment 4

[Dan Poirier [:dpoirier]]

I spent some time working on trying to get Mozillians running on Django 1.5. To use Django 1.5, we need to upgrade TastyPie (the library we use to provide our REST API), since the version of TastyPie we're using doesn't work with Django 1.5. However, the next minor version of TastyPie has significant backward-incompatible changes that break us in multiple ways, some of which I was unable to solve after spending hours digging into the breaks.

We are planning to change to a different library to provide our API (maybe django-rest-framework), so further time trying to support a newer TastyPie version seems wasteful. I think instead we should prioritize switching API libraries, so that we can move ahead on Django 1.5 that way.

Comment 5

[[github robot]]

Commit pushed to master at https://github.com/mozilla/mozillians

https://github.com/mozilla/mozillians/commit/2ba77e90b31617e99e70b12538a6dd19d09853a5
[fix bug 845593] Update Playdoh and upgrade to Django 1.5.5

Django 1.5.5 compatibility changes.

Comment 6

[Giorgos Logiotatidis [:giorgos]]

I merged this (along with bug 965828) into master today and did some exploratory testing on _dev_. Specifically I tested:

- login
- logout
- edit profile
- join group
- leave group
- create group
- delete group
- register
- delete profile
- vouch
- search
- privacy settings
- api queries as community app
- api queries as mozilla app

And all looks to be working fine. I'll push to _stage_ so other testers can verify.

Comment 7

[Justin Crawford [:hoosteeno] [:jcrawford]]

On _dev_...

in the front end of the site, I...
* created a profile
* logged in
* vouched an unvouched profile
* created a group
* deleted someone from a group
* invited someone
* joined a group
* left a group
* deleted a group

in the backend, I
* logged in
* merged a group
* changed a group
* created an announcement
* deleted an announcement

All looked good to me!

Comment 8

[William Reynolds [:williamr]]

I did some exploratory testing and everything behaved as expected. I tested:
- login
- logout
- edit profile
- join group
- leave group
- create group
- delete group
- search

Comment 9

[Matt Brandt [:mbrandt]]

Bumping to verified as [qa-] -- per comment 8 as well as automated tests continuing to report the site being in good shape