Code

Changes between Version 262 and Version 263 of BackwardsIncompatibleChanges


Ignore:
Timestamp:
09/09/08 22:48:40 (6 years ago)
Author:
adrian
Comment:

Updated page to note we're at 1.0.

Legend:

Unmodified
Added
Removed
Modified
  • BackwardsIncompatibleChanges

    v262 v263  
    11= Backwards-incompatible changes = 
    22 
    3 As Django is still in pre-1.0 mode, we haven't yet committed to maintaining backwards compatibility in any APIs. Although we're keeping such changes to a minimum, Django developers should be acutely aware of these changes. 
    4  
    5 Of course, once we reach 1.0, we'll be strongly committed to backward compatibility. 
    6  
    7 This page lists all backwards-incompatible changes to Django since the 0.96 release. For changes prior to 0.96, see the OlderBackwardsIncompatibleChanges page. 
     3This section of the Django wiki documents all backwards-incompatible changes to Django over the years. Now that Django has reached version 1.0, its APIs will remain stable until version 2.0. ***If you're already running Django 1.0, you need not worry about anything on this page.*** 
     4 
     5This page lists all backwards-incompatible changes to Django since the 0.96 release. Django historians, you can view pre-0.96 changes on the OlderBackwardsIncompatibleChanges page. 
     6 
     7For *future* backwards-incompatible changes -- that is, features that will be removed in version 2.0 -- see the FutureBackwardsIncompatibleChanges page. 
    88 
    99[[TOC(inline, depth=1)]]