Ticket #1944 (closed defect: fixed)
Extensions Migration path from 2.1.0 to 2.1.0
|Reported by:||robe||Owned by:||robe|
I'm planning to implement my workardoun to encourage testing of pre-versioned builds.
The plan -- always have a
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.