Make NAV's Django code work with Django 1.0

Bug #260554 reported by Stein Magnus Jodal
Affects Status Importance Assigned to Milestone
Network Administration Visualized
Fix Released
Stein Magnus Jodal

Bug Description

Django 1.0 is targeted for release September 2 2008 (current release is beta-1). To jump from the version NAV are currently using (SVN r7534) to 1.0, some changes have to be made to the Django code in NAV. contains details of the about 30 backwards incompatible changes done to Django between our current version and Django 1.0. We should do this jump before the release of NAV 3.5.0 in September 2008.

Changed in nav:
assignee: nobody → jodal
importance: Undecided → High
milestone: none → v3.5.0
status: New → Confirmed
Revision history for this message
Stein Magnus Jodal (jodal) wrote :

Django 1.0b1 is now installed at navdev. INSTALL file has been updated and BackwardsIncompatibleChanges worked through. Only change to the default branch was newforms/forms import in ipdevinfo.

The useradmin branch needs to fix newforms/forms too. I believe adamcik is fixing ATM.

Changed in nav:
status: Confirmed → In Progress
Revision history for this message
Stein Magnus Jodal (jodal) wrote :

Now fixed in the useradmin branch too. Everything seems to work nicely.

Changed in nav:
status: In Progress → Fix Committed
Changed in nav:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers