[postgis-devel] Small boo boo

[Kevin Neufeld]

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

Paragon Corporation wrote:
> Correct - well still under consideration. I think its rare we make changes
> to the sql file except when introducing new functions (which we aren't going
> to do anymore in microversions) so I suspect it won't be that much of an
> issue if we for simplicity make that requirement.
> 
> The only case I can think of where this becomes a big issue is if we start
> introducing a lot of sql/plpgsql functions from user contributions and those
> are constantly under maintenance.  Given that lots of people can do this, I
> suspect that would take on a life of its own anyway and shouldn't be
> packaged as part of PostGIS core.  Maybe we would do packages like R does.
> 
> Thanks,
> Regina
> 
> -----Original Message-----
> From: postgis-devel-bounces at postgis.refractions.net
> [mailto:postgis-devel-bounces at postgis.refractions.net] On Behalf Of strk
> 
> So if a bug is found in the implementation of an SQL or PL/PGSQL function we
> can't release a micro version upgrade ?
> 
> --strk; 
>