[postgis-tickets] [PostGIS] #2518: Upgrade instructions in manuals assume you are in a development version

[PostGIS]

#2518: Upgrade instructions in manuals assume you are in a development version
----------------------------+-----------------------------------------------
  Reporter:  strk           |       Owner:  robe         
      Type:  defect         |      Status:  closed       
  Priority:  medium         |   Milestone:  PostGIS 2.1.1
 Component:  documentation  |     Version:  2.0.x        
Resolution:  wontfix        |    Keywords:               
----------------------------+-----------------------------------------------
Changes (by robe):

  * status:  new => closed
  * resolution:  => wontfix


Comment:

 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.

-- 
Ticket URL: <http://trac.osgeo.org/postgis/ticket/2518#comment:2>
PostGIS <http://trac.osgeo.org/postgis/>
The PostGIS Trac is used for bug, enhancement & task tracking, a user and developer wiki, and a view into the subversion code repository of PostGIS project.