<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;} </style>
</head>
<body dir="ltr">
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<div class="section">
<h3><span style="font-size: 12pt;"><span style="font-weight: normal;">I missed this from the webpage I linked in the previous email:</span></span><br>
</h3>
<h3><a class="toc-backref" href="https://www.python.org/dev/peps/pep-0440/#id40">Implicit post releases</a></h3>
<p>Post releases allow omitting the <tt class="docutils literal">post</tt> signifier all together. When using this form the separator MUST be
<tt class="docutils literal">-</tt> and no other form is allowed. This allows versions such as
<tt class="docutils literal"><span class="pre">1.0-1</span></tt> to be normalized to
<tt class="docutils literal">1.0.post1</tt>. This particular normalization MUST NOT be used in conjunction with the implicit post release number rule. In other words,
<tt class="docutils literal">1.0-</tt> is <em>not</em> a valid version and it does
<em>not</em> normalize to <tt class="docutils literal">1.0.post0</tt>.</p>
</div>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
So 2.8.0-1 would be an allowed version number after all so that would be another option for a tag.<br>
</div>
<div id="appendonsend"></div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>From:</b> Christian Engwer <christian.engwer@uni-muenster.de><br>
<b>Sent:</b> 26 November 2021 08:48<br>
<b>To:</b> Dedner, Andreas <A.S.Dedner@warwick.ac.uk><br>
<b>Cc:</b> Markus Blatt <markus@dr-blatt.de>; dune-devel@lists.dune-project.org <dune-devel@lists.dune-project.org><br>
<b>Subject:</b> Re: [Dune-devel] vX.Y.Z.alpha tags</font>
<div> </div>
</div>
<div class="BodyFragment"><font size="2"><span style="font-size:11pt;">
<div class="PlainText">> All we're asking is for a mechanism to provide upgrades to the pypi packages that allow us to tell users for are now working with a buggy package to simply run<br>
> pip install --upgrade<br>
> to get a bugfix in the same way we would tell C++ users on the release branch to do git pull if we fixed a bug.<br>
> We would have preferred to have a well-defined state in the repositories to do that if possible.<br>
<br>
IMHO if the code in the dune-common is broken for a part of the<br>
feature set (e.g. for python bindings) and we have now a fix, this<br>
qualifies for a quick bug-fix release. And then also the versioning would be clear.<br>
<br>
The situation in Debian (as it was mentioned before) is different, as<br>
the source code it self didn't change, but the package information<br>
that are managed separately have changed. Thus it is not possible to<br>
reflect these changes in the version number of the software, but the<br>
package appends this infot via a '-1', '-2', etc. to the package<br>
version.<br>
<br>
Ciao<br>
Christian<br>
<br>
PS: great that dune works now via pypi! Thanks :-)<br>
</div>
</span></font></div>
</body>
</html>