[postgis-devel] Small boo boo

[Paragon Corporation]

I guess I'm thinking how many times have we really needed to change a .sql
file after releasing the first minor release aside from the cases where we
were introducing new functions which we will no longer be doing in micro
versions.

I can't think of any cases off hand.  So my point is that if we assume this
is the case moving forward, making the requirement that people have to
install an upgrade script when moving from micro to micro becomes
unnecessary and simplifies the nagging questions

I'm moving from 1.5.0 to 1.5.2 do I need to run a soft upgrade script --> NO
I'm moving from 1.5.0 to 1.6.2 do I need to run a soft upgrade script -->
YES

(You need to revert to a previous micro for some strange reason -- just
revert your .so/dll file) no .sql logic to roll back

I'm moving from 1.5 to 2.0 do I need to run an upgrade script --> You need
to do a hard upgrade

Thanks,
Regina


-----Original Message-----
From: postgis-devel-bounces at postgis.refractions.net
[mailto:postgis-devel-bounces at postgis.refractions.net] On Behalf Of Paragon
Corporation
Sent: Friday, August 21, 2009 2:51 PM
To: 'PostGIS Development Discussion'
Subject: Re: [postgis-devel] Small boo boo


> Really?  I guess I'm still confused on this.  I thought the purpose of
micro releases is to fix bugs.  You're saying this isn't the case?  Do > we
have these policies/guidelines listed on the developer's wiki somewhere (I
couldn't find them)?

> -- Kevin

You are right of course.  Purpose of micro versions is to fix bugs.  I'm
just thinking out loud.  Its not a policy we have agreed on.

My point is that if we want to be able to say for a micro version -- just
drop in the new so/dll and forget about it, we can't have stuff changing in
.sql files.  So ideally would be nice if we can avoid it since its something
a lot of people forget to run anyway and rarely should need to for a micro
version.  Then again if we need to do this then my whole having script check
only minor version and micro goes out the door since our micro scripts could
be different from the first minor script.

Thanks,
Regina



_______________________________________________
postgis-devel mailing list
postgis-devel at postgis.refractions.net
http://postgis.refractions.net/mailman/listinfo/postgis-devel