<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>This sounds like a reasonable way:</p>
<p>- If something in the code (in python / c++ / buildsystem) is
fixed that influences the user of the code whether downloaded by
git, by tar.gz or as python package, it should be a bugfix
release. This should then include a tar.gz package, maybe a new
entry in the webpage. We should make the burden for this as small
as possible.<br>
- If just "metadata" is updated that is required by external
environments, like pypi, we could add the post release suffix.
There, no need for a long procedure is required, just a tag would
be enough.<br>
</p>
<p><br>
</p>
<p>Best,<br>
Simon<br>
</p>
<p><br>
</p>
<div class="moz-cite-prefix">Am 26.11.21 um 09:50 schrieb Dedner,
Andreas:<br>
</div>
<blockquote type="cite"
cite="mid:VE1PR01MB62068C9D4DF9E74C47A6AAEE9A639@VE1PR01MB6206.eurprd01.prod.exchangelabs.com">
<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>
<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"
moz-do-not-send="true">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>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font style="font-size:11pt"
face="Calibri, sans-serif" color="#000000"><b>From:</b>
Christian Engwer <a class="moz-txt-link-rfc2396E" href="mailto:christian.engwer@uni-muenster.de"><christian.engwer@uni-muenster.de></a><br>
<b>Sent:</b> 26 November 2021 08:48<br>
<b>To:</b> Dedner, Andreas <a class="moz-txt-link-rfc2396E" href="mailto:A.S.Dedner@warwick.ac.uk"><A.S.Dedner@warwick.ac.uk></a><br>
<b>Cc:</b> Markus Blatt <a class="moz-txt-link-rfc2396E" href="mailto:markus@dr-blatt.de"><markus@dr-blatt.de></a>;
<a class="moz-txt-link-abbreviated" href="mailto:dune-devel@lists.dune-project.org">dune-devel@lists.dune-project.org</a>
<a class="moz-txt-link-rfc2396E" href="mailto:dune-devel@lists.dune-project.org"><dune-devel@lists.dune-project.org></a><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>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
Dune-devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Dune-devel@lists.dune-project.org">Dune-devel@lists.dune-project.org</a>
<a class="moz-txt-link-freetext" href="https://lists.dune-project.org/mailman/listinfo/dune-devel">https://lists.dune-project.org/mailman/listinfo/dune-devel</a>
</pre>
</blockquote>
<pre class="moz-signature" cols="72">--
Dr. Simon Praetorius
Technische Universität Dresden
Institute of Scientific Computing
phone: +49 351 463-34432
mail: <a class="moz-txt-link-abbreviated" href="mailto:simon.praetorius@tu-dresden.de">simon.praetorius@tu-dresden.de</a>
web: <a class="moz-txt-link-freetext" href="https://tu-dresden.de/mn/math/wir/das-institut/beschaeftigte/simon-praetorius">https://tu-dresden.de/mn/math/wir/das-institut/beschaeftigte/simon-praetorius</a></pre>
</body>
</html>