[Proj] Current master still at released 4.9.3?

Kristian Evers kreve at sdfe.dk
Fri Sep 29 03:07:20 EST 2017

proj.h has a different version number, but probably not the correct one either:


My guess is that no one really thought about changing version numbers. I agree that it is confusing. 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?


On Thu, Sep 28, 2017 at 11:03 PM +0200, "Mateusz Loskot" <mateusz at loskot.net<mailto:mateusz at loskot.net>> wrote:


TL;TR: Shouldn't the current master be at 4.9.3 plus 'one'?

I'm very late to the party since PROJ.4 moved to GitHub and
I also haven't been able to find any related posts in the archives,
(apart from the talk about 4.10.0 as next), sorry I'm missing
versioning/tagging policies.

The current release is 4.9.3, it is tagged in the repo.

But, in the master, the 'big four' still declares 4.9.3


Isn't it confusing that the development head declares the same
version as the released one?
Shouldn't master be one step ahead?

I'm not discussing what it should, 4.9.4 or 4.10.0, it doesn't
really matter for development/unreleased branch, I think.

Best regards,
Mateusz Loskot, http://mateusz.loskot.net
Proj mailing list
Proj at lists.maptools.org

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.maptools.org/pipermail/proj/attachments/20170929/28ca3896/attachment.htm 

More information about the Proj mailing list