[Proj] Current master still at released 4.9.3?
mcochran at athensal.us
Thu Sep 28 16:18:14 EST 2017
There was a somewhat related discussion about the next version number that
started on Jun 22. Thread top link:
I don't remember the outcome, but I don't think there was a consensus. The
version number may reflect API changes that are backward
On Thu, Sep 28, 2017 at 4:00 PM, Mateusz Loskot <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...
More information about the Proj