[postgis-devel] PSC Vote: Change PostGIS library name to drop the minor

[Mark Cave-Ayland]

On 29/08/17 14:55, Stephen Frost wrote:

>> These are not bug fixes but totally new functionality.
> 
> Adding new functionality isn't changing existing behavior.
> 
>> Your argument doesn't make sense to me.  Of course there is a difference and
>> people will know it when they do
>>
>> SELECT postgis_full_version();
> 
> If there's no change to existing behaviour except for clear bug fixes,
> then that seems like it would be alright to me, but it wasn't clear to
> me that Mark was saying that.  Perhaps we're just talking past each
> other here.  Adding new functionality in a new version should be fine to
> do, and is how most libraries operate when it comes to versioning.
> 
> If there is any chance that a given change will impact the ABI of an
> existing function, however, that needs to be handled differently and
> made clear so that users aren't upgraded automatically to the new
> version.
> 
> Hopefully that helps clarify my concern.

Yes, that's generally the way we've always tried to operate in the past,
i.e. fixes to algorithms are always accepted in micro versions and ABI
changes trigger a bump in minor version. Then again my free time is
sadly more limited these days so I haven't been tracking the repository
too closely...


ATB,

Mark.