vitcpp
commented
1 year ago Dear All, I would like to agree on versioning of pgsphere:
- In general, we should follow some principles described in https://semver.org/
- Major number is for API incompatible changes.
- Minor number is for API backward compatible changes (old user sql should work with newest pgsphere).
- Patch number is for bug fixes (API is untouched).
- Mark each version with annotated tag like v1.2.0
What I'm concerned, now we increment only the third number (patch number) for those changes that include API changes. I guess we should increment minor number in this case. But if we decide to increment minor number on each API small change this number may become too big.
One more question - should we increment minor or patch number each time when merging a new PR or introduce release plan?
Another issue is an optional compilation of some parts like healpix. I do not exclude that some new optional compilation will appear in the near future. I think it should be the user responsibility how to compile. The version number should not reflect how pgsphere is compiled. I see the only issue - upgrade scripts. I guess we may implement some query function that returns the list of compiled features. It may help upgrade script to decide what to do.
I appreciate any comments, thank you!
esabol
Introduce releases