<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:3.0cm 2.0cm 3.0cm 2.0cm;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="DA" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal"><span lang="EN-US">All,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">I have prepared a release schedule for the coming year. As always this is managed on GitHub [0]. For convenience, here’s an overview of the planned releases:<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">6.0.1 May 1<sup>st</sup> 2019<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">6.0.2 July 1<sup>st</sup> 2019<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">6.1.0 September 1<sup>st</sup> 2019<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">6.1.1 November 1<sup>st</sup> 2019<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">6.1.2 January 1<sup>st</sup> 2020<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">6.1.3 March 1<sup>st</sup> 2020<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">7.0.0 March 1<sup>st</sup> 2020<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Since the 6.0.0 release introduced massive amounts of new code I expect more bugs to be revealed than usually, hence the higher frequency of bug fix releases (every two months, unless a minor version release is scheduled).
Note that 6.1.3 and 7.0.0 is planned for release on the same day. Since 7.0.0 will remove the proj_api.h header I expect that version 6 will be seen in the wild for quite some time after the 7.0.0 release and have therefore scheduled an additional bug fix
release of the 6.1 branch. The maintenance status of the 6.1 branch should be re-evaluated once we are close to the release of 7.0.0. It may be necessary to issue a few more bug fix release based on the 6.1 branch until downstream projects has moved away from
using the proj_api.h API.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">The development strategy will be the same as we have used for the last couple of years: All changes are committed to the master branch and bug fixes will be cherry-picked into the relevant maintenance branch. As a consequence
of this, development on version 7 cannot start before September 1<sup>st</sup>. This should not be a problem as the planned breaking changes for 7.0 at this time only consist of removing of proj_api.h – a task that is relatively easy to perform.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Please let me know if you have any comments or suggestions for changes.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">/Kristian<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">[0] <a href="https://github.com/OSGeo/proj.4/milestones?direction=asc&sort=due_date&state=open">
https://github.com/OSGeo/proj.4/milestones?direction=asc&sort=due_date&state=open</a><o:p></o:p></span></p>
</div>
</body>
</html>