[Dune-devel] Protected branches for dune-common

[Dedner, Andreas]

I can't remember this even being discussed and decided on. I did one of the previous releases and can't remember having to treat dune-common differently.
I would vote to change this for now and if somebody thinks it's a good idea, then we should discuss that and possibly change the settings for all core module if there are good reasons to do so.
Andreas
________________________________
From: Dune-devel <dune-devel-bounces at lists.dune-project.org> on behalf of René Heß <rene.hk-edv at gmx.de>
Sent: 12 July 2021 09:24
To: 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] Protected branches for dune-common

Hi Markus,

looking at the protected branches in

https://gitlab.dune-project.org/core/dune-common/-/settings/repository

releases/* is indeed protected and no one is allowed to push them. You
are owner in dune-common so you already have the highest access role so
you could change that.

The alternative would be creating a new branch and merging it into the
releases/2.8 branch.

I did not change anything as it seems to be intentional and I'm not in a
position to change the behaviour (in the sense of 'I should not', as a
gitlab admin I could of course). Just pointing out the current state :).


Thanks for working on the release,
best regards,
René





Markus Blatt <markus at dr-blatt.de> writes:

> Hi,
>
> can somebody please give me push rights to releases/2.8 in dune-common? Without that it is rather
> cumbersome to do a release. Maybe I am in the wrong group?
>
> Markus
>
> _______________________________________________
> 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/20210712/19e1d1ba/attachment.htm>