[postgis-devel] [PostGIS] #275: documentation still points to Google bug-tracker

[PostGIS]

#275: documentation still points to Google bug-tracker
----------------------+-----------------------------------------------------
  Reporter:  nicklas  |       Owner:  pramsey      
      Type:  defect   |      Status:  closed       
  Priority:  medium   |   Milestone:  postgis 1.3.7
 Component:  postgis  |     Version:               
Resolution:  fixed    |    Keywords:               
----------------------+-----------------------------------------------------
Comment (by robe):

 Nicklas,

 You have a point.  I think maybe we should just drop the micro from our
 documentation and have it called manual-1.4SVN

 However I still think our released documentation should point at the
 actual released version.

 Here is why and I'm going to explain it really badly.

  A released freeze provides us (and package managers) a checkpoint as to
 what we can expect most everyone  will be using so we aren't dealing with
 slight differences in things.  The non-released stuff also has stuff
 subject to change -- like it has the link to unreleased 1.4.1 tar which
 would be confusing if you are assuming its the official doc.

 If you think about documentation like any other kind of source code, it is
 prone to the same problems. We could accidentally cut out whole sections
 or put in stuff for debate etc, because we aren't going to be quite as
 careful, knowing we will recheck it later before release. True it does
 have an advantage being online, but not everyone reads it online.

 Its the same reason why we still offer the 1.4.0 released version and
 everyone isn't rushing to use 1.4.1SVN even though it in theory is a more
 stable product than 1.4.0 RTM because it has all bug fixes for 1.4 and not
 much else)

-- 
Ticket URL: <http://trac.osgeo.org/postgis/ticket/275#comment:8>
PostGIS <http://trac.osgeo.org/postgis/>
PostGIS