[Proj] PROJ 5.0.0RC6

[Kristian Evers]

Thanks, I will do that!

/Kristian

> On 1 Mar 2018, at 20:21, Jeff McKenna <jmckenna at gatewaygeomatics.com> wrote:
> 
> Thanks Kristian.  Regarding the announcement, if you email the text you 
> need published to news_item(at)osgeo.org it will be magically sent 
> through Twitter, new website, Discuss list etc.
> 
> -jeff
> 
> 
> 
> On 2018-03-01 3:10 PM, Kristian Evers wrote:
>> Jeff,
>> 
>> That would also be the ideal case, I agree. The release process was started two days ago with the vote on the MetaCRS list.
>> Also, and this is actually the most pressing issue, my available time is limited the following weeks so I wouldn’t be able to
>> properly follow up on yet another RC.
>> 
>> Aside from the issue you have reported the release seem to be in good shape. There is a work around to the know issue
>> with the web mercator (remove +nadgrids=@null from the proj-string) so early adopters should be able to get going anyway.
>> 
>> I am sure more issues will rise to the surface once the final release is out in the wild. Those along with the web mercator
>> thing will be fixed in a short while in 5.0.1.
>> 
>> Don’t feel bad about improving the software! It is very appreciated and I can only hope that more will do the same in the future!
>> 
>> /Kristian
>> 
>>> On 1 Mar 2018, at 20:03, Jeff McKenna <jmckenna at gatewaygeomatics.com> wrote:
>>> 
>>> Anyway sorry that I caused all this grief with my testing.  Congrats on
>>> this massive release!!
>>> 
>>> -jeff
>>> 
>>> 
>>> 
>>> On 2018-03-01 2:52 PM, Jeff McKenna wrote:
>>>> 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
>>>>> 
> _______________________________________________
> Proj mailing list
> Proj at lists.maptools.org
> http://lists.maptools.org/mailman/listinfo/proj