<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body dir="auto">
But as one of the members with the maintain role (higher than triage and write), he has access to bypass permissions. If you go look back in the PR where I explained the branch rules, I showed the checkbox that allows to bypass for example in PRs. Here is the
public combined view of the rules that are active for releasebranch_8_3 <a href="https://github.com/OSGeo/grass/rules/270686?ref=refs%2Fheads%2Freleasebranch_8_3">https://github.com/OSGeo/grass/rules/270686?ref=refs%2Fheads%2Freleasebranch_8_3</a> and <a href="https://github.com/OSGeo/grass/rules?ref=refs%2Fheads%2Freleasebranch_8_3">https://github.com/OSGeo/grass/rules?ref=refs%2Fheads%2Freleasebranch_8_3</a>
<div><br>
</div>
<div>Note how they are different than <a href="https://github.com/OSGeo/grass/rules?ref=refs%2Fheads%2Fmain">https://github.com/OSGeo/grass/rules?ref=refs%2Fheads%2Fmain</a></div>
<div><br>
</div>
<div>It was made such as changing workflow requirements for main don’t restrict the older branches to be merged, or that changes in the CI infrastructure (outside of our repo) make it so they don’t work anymore. So they are kind of run on a best-effort basis,
instead of religiously. <br>
<div>
<div><br>
<div><br id="lineBreakAtBeginningOfSignature">
<div dir="ltr">Edouard Choinière</div>
<div dir="ltr"><br>
<blockquote type="cite">Le 20 févr. 2024 à 06:45, Nicklas Larsson <n_larsson@yahoo.com> a écrit :<br>
<br>
</blockquote>
</div>
<blockquote type="cite">
<div dir="ltr"> <br style="font-family: Menlo-Regular; font-size: 11px;">
<blockquote type="cite" style="color: rgb(0, 0, 0); font-family: Menlo-Regular; font-size: 11px;">
On 20 Feb 2024, at 10:14, Markus Neteler via grass-dev <<a href="mailto:grass-dev@lists.osgeo.org">grass-dev@lists.osgeo.org</a>> wrote:<br>
<br>
<br>
In fact the slowest CI run determines how much time I have to wait<br>
with each release step (i.e., editing VERSION file, wait 1:30hs, do<br>
some steps, wait 1:30hs, create tarball, wait 1:30hs, reset VERSION<br>
file, wait 1:30hs ... which is a pain).<br>
<br>
</blockquote>
<br style="font-family: Menlo-Regular; font-size: 11px;">
<span style="font-family: Menlo-Regular; font-size: 11px;">I agree this is a case where we have limited ourself too much, with all those </span><br style="font-family: Menlo-Regular; font-size: 11px;">
<span style="font-family: Menlo-Regular; font-size: 11px;">required 1.5 hrs tests, approval, etc. (not even [skip ci] would work) . What you</span><br style="font-family: Menlo-Regular; font-size: 11px;">
<span style="font-family: Menlo-Regular; font-size: 11px;">would need is a (ideally) direct commit access or at least “Rebase and merge”</span><br style="font-family: Menlo-Regular; font-size: 11px;">
<span style="font-family: Menlo-Regular; font-size: 11px;">option to merge (thus enable a number of commits to be merged at one time,</span><br style="font-family: Menlo-Regular; font-size: 11px;">
<span style="font-family: Menlo-Regular; font-size: 11px;">as opposed to "Squash and merge”).</span><br style="font-family: Menlo-Regular; font-size: 11px;">
<br style="font-family: Menlo-Regular; font-size: 11px;">
<span style="font-family: Menlo-Regular; font-size: 11px;">We must find a solution to improve this situation for preparing releases, I</span><br style="font-family: Menlo-Regular; font-size: 11px;">
<span style="font-family: Menlo-Regular; font-size: 11px;">wouldn’t mind temporary lifting necessary constraints.</span></div>
</blockquote>
</div>
</div>
</div>
</div>
</body>
</html>