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

[Dedner, Andreas]

What would a bugfix release require? Would it be enough to simply add the v2.8.1 tag using (more or less) the current release branch - that is of course fine with us. Or would we have to

  *   wait for everyone to decide what should be cherry-picked and which MR needs to be finished off
  *   build tarballs to upload to the website
  *   change all the dune.module files
  *   change all the module description files on the website to get an updated documentation
  *   and ...

I was hoping for an easy way which would allow me to tell Python users that they can simply run pip install --upgrade
the same way I can now already tell source users on the release branches to do git pull.
Best
Andreas


________________________________
From: Dune-devel <dune-devel-bounces at lists.dune-project.org> on behalf of Christoph Grüninger <foss at grueninger.de>
Sent: 25 November 2021 17:22
To: dune-devel at lists.dune-project.org <dune-devel at lists.dune-project.org>
Subject: Re: [Dune-devel] vX.Y.Z.alpha tags

Hi Andreas,
I would prefer to have a 2.8.1 release. Give people the chance to claim
things that should be back-ported. Then take the 2.8 branch, and make a
bugfix release 2.8.x. Having such bugfix releases more frequent is a
good thing anyway.

Bye
Christoph

_______________________________________________
Dune-devel mailing list
Dune-devel at lists.dune-project.org
https://lists.dune-project.org/mailman/listinfo/dune-devel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.dune-project.org/pipermail/dune-devel/attachments/20211125/083fab63/attachment.htm>