[postgis-devel] [PostGIS] #1944: Extensions Migration path from 2.1.0 to 2.1.0

[PostGIS]

#1944: Extensions Migration path from 2.1.0 to 2.1.0
-----------------------------------+----------------------------------------
 Reporter:  robe                   |       Owner:  robe         
     Type:  defect                 |      Status:  new          
 Priority:  medium                 |   Milestone:  PostGIS 2.1.0
Component:  build/upgrade/install  |     Version:  trunk        
 Keywords:                         |  
-----------------------------------+----------------------------------------
 I'm planning to implement my workardoun to encourage testing of pre-
 versioned builds.

 The plan -- always have a

 PostGIS-2.1.0SVN--PostGIS-2.10SVNnext.sql

 PostGIS-2.1.0SVNnext--PostGIS-2.1.0SVN.sql

 As I describe here:
 http://www.bostongis.com/blog/index.php?/archives/190-How-to-Use-PostGIS-
 Extensions-to-upgrade-to-non-released-PostGIS-versions.html

 So that way people who are using the extensions model, but also want to be
 able to upgrade non-released versions will play a yoyo game of

 {{{
 ALTER EXTENSION postgis UPDATE TO "2.1.0SVNnext";
 ALTER EXTENSION postgis UPDATE TO "2.1.0SVN";
 }}}

 Before I do this, we really got to fix the upgrade scripts (since they are
 broken both for extension and for 9.0 builds if you are coming from 2.0)
 so they actually work for early 2.1.0 releases and 2.0.+ releases. Without
 this I feel we aren't going to get any serious testing which is essential.

-- 
Ticket URL: <http://trac.osgeo.org/postgis/ticket/1944>
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.