[Dune-devel] vX.Y.Z.alpha tags

[Dedner, Andreas]

​I missed this from the webpage I linked in the previous email:
Implicit post releases<https://www.python.org/dev/peps/pep-0440/#id40>

Post releases allow omitting the post signifier all together. When using this form the separator MUST be - and no other form is allowed. This allows versions such as 1.0-1 to be normalized to 1.0.post1. This particular normalization MUST NOT be used in conjunction with the implicit post release number rule. In other words, 1.0- is not a valid version and it does not normalize to 1.0.post0.

So 2.8.0-1 would be an allowed version number after all so that would be another option for a tag.
________________________________
From: Christian Engwer <christian.engwer at uni-muenster.de>
Sent: 26 November 2021 08:48
To: Dedner, Andreas <A.S.Dedner at warwick.ac.uk>
Cc: Markus Blatt <markus at dr-blatt.de>; dune-devel at lists.dune-project.org <dune-devel at lists.dune-project.org>
Subject: Re: [Dune-devel] vX.Y.Z.alpha tags

> 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
>    pip install --upgrade
> 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.
> We would have preferred to have a well-defined state in the repositories to do that if possible.

IMHO if the code in the dune-common is broken for a part of the
feature set (e.g. for python bindings) and we have now a fix, this
qualifies for a quick bug-fix release. And then also the versioning would be clear.

The situation in Debian (as it was mentioned before) is different, as
the source code it self didn't change, but the package information
that are managed separately have changed. Thus it is not possible to
reflect these changes in the version number of the software, but the
package appends this infot via a '-1', '-2', etc. to the package
version.

Ciao
Christian

PS: great that dune works now via pypi! Thanks :-)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.dune-project.org/pipermail/dune-devel/attachments/20211126/2d494036/attachment-0001.htm>