[Proj] Time for a new release?

Greg Troxel gdt at lexort.com
Thu Nov 9 09:26:21 EST 2017

Kristian Evers <kreve at sdfe.dk> writes:

-----Oprindelig meddelelse-----
> Fra: proj-bounces at lists.maptools.org [mailto:proj-bounces at lists.maptools.org] På vegne af Roger Bivand
> Sendt: 9. november 2017 13:23
> Til: proj at lists.maptools.org
> Emne: Re: [Proj] Time for a new release?
> Could I please ask that the version in master be set to a value sorting after
> the current release? It doesn't have to be the actual value, but for
> downstream testing, it would be really convenient not to see the same value
> as the current release.

> I agree, that is something we should handle better after the next release.
> Kristian

I think the point is to change master now, so that packages built from
master will sort properly.

Currently we have 4.9.3.   Presumably the release is going to be 4.10 or
5.0 (absent anything drastic, 4.10 seems obviously right).

So, master can be changed right now to 4.9.80, following an ancient
scheme, which is understood to be an alpha of the next real release
after 4.9.  It sorts before 4.10, and after 4.9.3 (and is obviously not

Part of a release cycle is packagers preparing a package from a tarball
created from master, building that package, and testing it.  It's that
process that is almost certainly driving Roger's request.

The other thing that really helps is for the release tarball creation
process to be scripted and repeatable, with no manual steps, so that
packagers can create them for testing, and be sure that the actual
release will be identical (modulo intentionally changed content).

Greg (who looks after proj in pkgsrc)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 162 bytes
Desc: not available
Url : http://lists.maptools.org/pipermail/proj/attachments/20171109/5ae10d32/attachment.pgp 

More information about the Proj mailing list