[Proj] Current master still at released 4.9.3?

Mateusz Loskot mateusz at loskot.net
Fri Sep 29 03:31:12 EST 2017

On 29 September 2017 at 10:07, Kristian Evers <kreve at sdfe.dk> wrote:
> proj.h has a different version number, but probably not the correct one
> either:
> https://github.com/OSGeo/proj.4/blob/master/src/proj.h#L157
> My guess is that no one really thought about changing version numbers. I
> agree that it is confusing.

Perhaps one-for-all VERSION file would be better to maintain the number.

> Somehow indicating the development status of
> builds  that are made between releases would be nice.


> Perhaps by adding the commit hash to the version number?

IMO, version should always have X.Y.Z  format, without
any suffixes like -dev, etc.

AFAIK, typical practice is that after releasing X.Y.Z,
development branch bumps to X.Y+1.Z.

Why not bump to 4.10.0?
It wouldn't mean a promise to version next release as 4.10.0.
It would just mean the master is ahead of release.
If master introduces incompatible API, it may become 5.0.0,
it is unknown.

Best regards,
Mateusz Loskot, http://mateusz.loskot.net

More information about the Proj mailing list