<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
Idan,
<blockquote type="cite"
cite="mid:CAEDrt3_R3cKhN957uzNYQd-1NPLhNpjz_vmDvuy3dmezU1gZBw@mail.gmail.com">
<div dir="ltr">
<div>What is the policy for accepting feature PRs (not bug
fixes) ? </div>
<div>I mean do all new features from when beta/RC is published
will be merged only to the next minor version, i.e. 3.4 ?</div>
</div>
</blockquote>
<p>Between beta1 and RC1, some feature PRs might be accepted, but
not ones with strong impacts (typically should not require any
change in packaging build recipees)<br>
</p>
<p>At time RC1 is created, master becomes 3.4dev, and feature PRs
are only for master, and release/3.3 is branched. Bug fixes go in
master and release/3.3. If a severe enough bugfix is found after
RC1 and before final, then a RC2 might be issued.<br>
</p>
<blockquote type="cite"
cite="mid:CAEDrt3_R3cKhN957uzNYQd-1NPLhNpjz_vmDvuy3dmezU1gZBw@mail.gmail.com">
<div dir="ltr">
<div><br>
</div>
<div>Because we cannot release <a
href="https://pypi.org/project/gdal-utils/"
moz-do-not-send="true">gdal-utils</a> version 3.3.0 for that
version number had been used (and deleted to avoid further
confusion), I suggest we declare that:</div>
<div>gdal 3.3.0 + gdal_utils 3.3.0.x are beta (x>6);</div>
<div>gdal 3.3.1 + gdal_utils 3.3.1 will be the final release, </div>
<div>Does it make sense or is it too confusing ?</div>
</div>
</blockquote>
<p>A bit confusing. I do want a 3.3.0 final production ready GDAL
release. That the new gdal_utils pip package starts at 3.3.0.6 is
a bit unfortunate, but I can live with that. That will not break
anyone.<br>
</p>
<p>Even<br>
</p>
<pre class="moz-signature" cols="72">--
<a class="moz-txt-link-freetext" href="http://www.spatialys.com">http://www.spatialys.com</a>
My software is free, but my time generally not.</pre>
</body>
</html>