2
2
API stability
3
3
=============
4
4
5
- Django promises API stability and forwards-compatibility since version 1.0. In
6
- a nutshell, this means that code you develop against a version of Django will
7
- continue to work with future releases. You may need to make minor changes when
8
- upgrading the version of Django your project uses: see the "Backwards
9
- incompatible changes" section of the :doc:`release note </releases/index>` for
10
- the version or versions to which you are upgrading.
5
+ Django is committed to API stability and forwards-compatibility. In a nutshell,
6
+ this means that code you develop against a version of Django will continue to
7
+ work with future releases. You may need to make minor changes when upgrading
8
+ the version of Django your project uses: see the "Backwards incompatible
9
+ changes" section of the :doc:`release note </releases/index>` for the version
10
+ or versions to which you are upgrading.
11
+
12
+ At the same time as making API stability a very high priority, Django is also
13
+ committed to continual improvement, along with aiming for "one way to do it"
14
+ (eventually) in the APIs we provide. This means that when we discover clearly
15
+ superior ways to do things, we will deprecate and eventually remove the old
16
+ ways. Our aim is to provide a modern, dependable web framework of the highest
17
+ quality that encourages best practices in all projects that use it. By using
18
+ incremental improvements, we try to avoid both stagnation and large breaking
19
+ upgrades.
11
20
12
21
What "stable" means
13
22
===================
@@ -29,8 +38,8 @@ In this context, stable means:
29
38
See :ref:`official-releases` for more details on how Django's version
30
39
numbering scheme works, and how features will be deprecated.
31
40
32
- - We'll only break backwards compatibility of these APIs if a bug or
33
- security hole makes it completely unavoidable.
41
+ - We'll only break backwards compatibility of these APIs without a deprecation
42
+ process if a bug or security hole makes it completely unavoidable.
34
43
35
44
Stable APIs
36
45
===========
0 commit comments