[Proj] PROJ 5.0.0RC6

Jeff McKenna jmckenna at gatewaygeomatics.com
Thu Mar 1 13:52:20 EST 2018

Actually I assumed that this would call for an immediate RC7 release. 
(as it affects so many projects downstream, for [unfortunately] the most 
translated projection today).  -my thoughts, jeff

On 2018-03-01 2:18 PM, Kristian Evers wrote:
> I’ve been thinking about this all day. Initially I was planing to add the fix to the map server problem, but it is not
> particularly smart to add stuff without an RC I guess. The current release candidate seems to behave quite well,
> apart from that one thing which has a known work-around. I’ll plan for a patch release around April 1st. If the
> number of reported bugs is low I’ll consider not issuing 5.0.1.
> I’ll get to work on packing 5.0.0.
> /Kristian
>> On 1 Mar 2018, at 19:07, Sebastiaan Couwenberg <sebastic at xs4all.nl> wrote:
>> On 03/01/2018 06:39 PM, Kristian Evers wrote:
>>> Well, I was sort of going to play It by ear with regards to patch releases. 5.1.0 will be around June 1st.
>>> But maybe it isn’t such a bad idea to already schedule the first pure bug-fixing release in a month time or so.
>>> Jeff’s (well.. my bug, discovered by Jeff) could then be applied in that release instead of sneaking
>>> It in the final release. The vote promoting RC6 to final has more or less passed on the MetaCRS list
>>> less than an hour ago.
>>> See the release schedule here: https://github.com/OSGeo/proj.4/milestones?direction=asc&sort=due_date&state=open
>>> What are your thoughts on that?
>> The next release in June is quite reasonable, although not strictly a
>> bugfix release.
>> If there aren't many regressions reported before that time, leaving the
>> planned release dates as-is is probably fine.
>> Otherwise scheduling a bugfix release before that time, 4-6 weeks after
>> the 5.0.0 release, is probably a good idea.
>> Kind Regards,
>> Bas
>> ________

More information about the Proj mailing list