From cc76fb3dff13fd18327a850e09be62b6b79e8c28 Mon Sep 17 00:00:00 2001 From: Christian Pedersen Date: Wed, 14 Oct 2015 14:07:34 +0200 Subject: [PATCH] Version 1 now exists --- docs/versioning.rst | 9 +++------ 1 file changed, 3 insertions(+), 6 deletions(-) diff --git a/docs/versioning.rst b/docs/versioning.rst index fffa68b33..6ae9ce981 100644 --- a/docs/versioning.rst +++ b/docs/versioning.rst @@ -12,8 +12,7 @@ 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. So far, only zero is available for *A* as Scrapy hasn't yet - reached 1.0. + 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. @@ -27,12 +26,10 @@ For example: API Stability ============= -API stability is one of Scrapy major goals for the *1.0* release, which doesn't -have a due date scheduled yet. +API stability was one of the major goals for the *1.0* release. Methods or functions that start with a single dash (``_``) are private and -should never be relied as stable. Besides those, the plan is to stabilize and -document the entire API, as we approach the 1.0 release. +should never be relied as stable. Also, keep in mind that stable doesn't mean complete: stable APIs could grow new methods or functionality but the existing methods should keep working the