Details
-
Bug
-
Resolution: Fixed
-
Test Blocker
-
4.1, 4.5
-
*Location*: http://developer.couchbase.com/documentation/server/4.1/install/upgrading.html
*User-Agent*: Mozilla/5.0 (X11; Linux i686; rv:45.0) Gecko/20100101 Firefox/45.0
*Referrer*: http://developer.couchbase.com/documentation/server/4.1/install/install-platforms.html
*Screen Resolution*: 1920 x 1080
*Location*: http://developer.couchbase.com/documentation/server/4.1/install/upgrading.html *User-Agent*: Mozilla/5.0 (X11; Linux i686; rv:45.0) Gecko/20100101 Firefox/45.0 *Referrer*: http://developer.couchbase.com/documentation/server/4.1/install/install-platforms.html *Screen Resolution*: 1920 x 1080
Description
page states.. "You can upgrade Couchbase Server from one major version to another. For example, you can upgrade directly from version 3.0.3 to 4.0.0, and also from version 2.5.2 to 4.0.0."
- upgrading 2.5.2 to 4.0.0 is supported but it's not one major to another.
This was true in earlier versions of Couchbase where we only supported 1.x -> 2.x and 2.x -> 3.x for instance.
But now we support upgrading across major versions 2.x -> 4.x
also states.. "Products that have passed the expiration point or end of life date are not supported in the upgrade path. First upgrade to a supported version that has not reached its end of life, and then follow the upgrade path."
- This isn't true, we support upgrading from EOL in the upgrade path. How else would you get off a EOL version if upgrading from an EOL isn't supported ?
- The example above, upgrading from 3.0.3 and 2.5.2 to 4.0.0.... both 3.0.3 and 2.5.2 are EOL.