Remove mention of odd-numbered versions for development releases

Fixes GH-1317
This commit is contained in:
Paul Tremberth 2016-09-20 18:14:43 +02:00
parent eb49b459c1
commit 40293551b2
1 changed files with 16 additions and 5 deletions

View File

@ -7,22 +7,33 @@ Versioning and API Stability
Versioning
==========
Scrapy uses the `odd-numbered versions for development releases`_.
There are 3 numbers in a Scrapy version: *A.B.C*
* *A* is the major version. This will rarely change and will signify very
large changes.
* *B* is the release number. This will include many changes including features
and things that possibly break backwards compatibility. Even Bs will be
stable branches, and odd Bs will be development.
and things that possibly break backwards compatibility, although we strive to
keep theses cases at a minimum.
* *C* is the bugfix release number.
Backward-incompatibilities are explicitly mentioned in the :ref:`release notes <news>`,
and may require special attention before upgrading.
Development releases do not follow 3-numbers version and are generally
released as ``dev`` suffixed versions, e.g. ``1.3dev``.
.. note::
With Scrapy 0.* series, Scrapy used `odd-numbered versions for development releases`_.
This is not the case anymore from Scrapy 1.0 onwards.
Starting with Scrapy 1.0, all releases should be considered production-ready.
For example:
* *0.14.1* is the first bugfix release of the *0.14* series (safe to use in
* *1.1.1* is the first bugfix release of the *1.1* series (safe to use in
production)
API Stability
=============