Upgrade instructions in manuals assume you are in a development version

[strk]

Both this: ​http://postgis.net/docs/manual-2.0/postgis_installation.html#soft_upgrade and this: ​http://postgis.net/docs/manual-2.1/postgis_installation.html#soft_upgrade

In the "with extension" section, assume you are running a development version:

ALTER EXTENSION postgis UPDATE TO "2.0.5SVN";
ALTER EXTENSION postgis_topology UPDATE TO "2.0.5SVN";

ALTER EXTENSION postgis UPDATE TO "2.1.1dev";
ALTER EXTENSION postgis_topology UPDATE TO "2.1.1dev";

Don't we want _stable_ release instructions ?

[robe]

those are all autogenerated based on version included. It's much easier to figure out you are not running a dev if you are not running a dev don't you think than what upgrade is a development version.

The PDFs and html docs that get autogenerated when we push a release have the right update statement. I'd like to keep it that way.

Currently we only show the Branch Stable (not the released version) of the docs. Now this brings up the question of we need to put back released versions of the docs. I would tend to say no just because it adds clutter and I don't think people are that stupid to think if they know they are running released that they should upgrade to dev.

[strk]

I think documentation for official releases should be accessible under ​http://postgis.net/documentation. That's what I'd expect as a user. Or the manual should be "micro version agnostic" to avoid confusion, and specifically mention "Substitute X.Y.Z with the version of PostGIS you're using"

[robe]

I like the substitute option disclaimer. Part of the reason we have doco having not released is so people can see updated content like notes about issues that may affect them etc we add before next release.