CURRENT VERSION OF API STABILITY POLICY:

The release of Django 1.0 comes with a promise of API stability and
forwards-compatibility. In a nutshell, this means that code you
develop against Django 1.0 will continue to work against 1.1
unchanged, and you should need to make only minor changes for any 1.X
release.



SUGGESTED VERSION OF API STABILITY POLICY:

The release of Django 1.0 comes with a promise of API stability and
forwards-compatibility. In a nutshell, this means that code you
develop against Django 1.0 will continue to work against 1.1
unchanged, and you should need to make only minor changes for the 1.2
release.



It seems that this small change alone could dramatically decrease the
number of hours spent by you guys.

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-develop...@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Reply via email to