innov
/
django1
1
0
Fork 0
Code Issues Pull Requests 1 Projects Releases Wiki Activity

Clarified wording about deprecated features (thanks, Wilson) 

git-svn-id: http://code.djangoproject.com/svn/django/trunk@1491 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
Jacob Kaplan-Moss 2005-11-29 15:30:06 +00:00
parent 3373447fba
commit 568a926452
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/contributing.txt
View File

@ -234,8 +234,8 @@ Django's release numbering works as follows:
feature in version ``A.B`` is deprecated, it will continue to work in feature in version ``A.B`` is deprecated, it will continue to work in
version ``A.B+1``. In version ``A.B+2``, use of the feature will raise a version ``A.B+1``. In version ``A.B+2``, use of the feature will raise a
``PendingDeprecationWarning`` but will continue to work. Version ``PendingDeprecationWarning`` but will continue to work. Version
``A.B+3`` will remove the feature entirely. However, a release of version ``A.B+3`` will remove the feature entirely. Major point releases will
``A+1`` will remove the feature entirely. always remove deprecated features immediately.
* ``C`` is the micro version number which, is incremented for bug and * ``C`` is the micro version number which, is incremented for bug and
security fixes. A new micro-release will always be 100% security fixes. A new micro-release will always be 100%