<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">This is mostly a service announcement to PROJ devs, but might also be relevant for other.<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">As mentioned in an earlier email I want to put out a patch release around April 1<sup>st</sup>, which will
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">be version 5.0.1. This will only be fixes to bugs in 5.0.0. I have created a 5.0 branch in the git
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">repository and plan on cherry-picking commits to master that fixes bugs in 5.0.0. Pull requests<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">or issues to these commits will be tagged with the 5.0.1 milestone on GitHub. I’ll try to be on<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">top of things but in case I miss something please add the 5.0.1 milestone so I know that there<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">are commits to be cherry-pick into the 5.0 branch.<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">In general I intend to use the milestones system on GitHub a lot more going forwards. It makes it<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">a lot easier to plan what’s coming up and keep track of what’s gone into a new release. Pull requests<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">or issues that relate to commits which fixes bugs or adds new functionality should always be tagged<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">with the relevant milestone. The list of milestones/releases for next few years can be found here:<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"><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>
<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>
</div>
</body>
</html>