On 10/18/15 6:43 PM, Jeff Janes wrote:
It seems like there should be some way to mark a feature-release of an
extension, versus a server-compatibility-only release (also versus a
bug-fix-in-extension release).
The problem is worse than that: the 'version' string for an extension is
just
On Fri, Oct 9, 2015 at 1:36 AM, Albe Laurenz
wrote:
> Jeff Janes wrote:
> > I am facing a scenario where I have different version of an extension,
> say 1.0 and 2.0, which have
> > some different functionality between them (so not merely a bug fix), so
> people might
Jeff Janes wrote:
> I am facing a scenario where I have different version of an extension, say
> 1.0 and 2.0, which have
> some different functionality between them (so not merely a bug fix), so
> people might want to continue
> to use 1.0.
>
> But changes to the PostgreSQL software between
I am facing a scenario where I have different version of an extension, say
1.0 and 2.0, which have some different functionality between them (so not
merely a bug fix), so people might want to continue to use 1.0.
But changes to the PostgreSQL software between major versions requires
changes to