Changes between Version 1 and Version 2 of Ticket #16778, comment 7


Ignore:
Timestamp:
01/05/12 05:38:07 (3 years ago)
Author:
ramiro
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #16778, comment 7

    v1 v2  
    1414The good news is that you can apply this four-line patch by yourself to your copy of Django. By doing this:
    1515
    16 * You know there is not other change to 1.3.1 than the fix for this issue (some shops have policies about only using officially released versions of software, this would mean breaking that but OTOH this item means you can keep risks low when you have heavily invested and tested 1.3.1)
     16* You know there is no other change to 1.3.1 apart than this fix (some shops have policies about only using officially released versions of software, this would mean breaking that but OTOH this item means you can keep risks low when you have heavily invested in and tested 1.3.1)
    1717* You don't have to wait for Django 1.3.2
    1818* You don't have to wait for Django 1.4
    1919
    20 In practice, a line needs to be drawn regarding compatibility with features of other parts of the stack. Django 1.3 was releases in March 2011 and Postgres 9.1 in September 2011. If every release of Django would need to be updated for every change of behavior of every new version piece of software that appear in every new OS release, the task of adapting to them would be a never ending one. That's what the development trunk in the repository is for.
     20In practice, a line needs to be drawn regarding compatibility with features of other parts of the stack. Django 1.3 was releases in March 2011 and Postgres 9.1 in September 2011. If every release (or its corresponding maintenance branch) of Django had to be updated for every change of behavior of every new version of every piece of the software stack that appears in every new OS release, then the task of adapting to them would be a never ending one and
     21
     22 a. Would increase risks of regressions/unintended changes of behavior (we have been bitten by this in the past)
     23 b. Would divert resources from development in trunk.
Back to Top