[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    Re: Possible to move some KF5 frameworks to invent?
From:       Albert Vaca Cintora <albertvaka () gmail ! com>
Date:       2019-08-12 10:53:26
Message-ID: CAAQViEuSEF4q1AsE30GS4eAiqHHA6xf8j1TyBpOhtC3eRTkbhg () mail ! gmail ! com
[Download RAW message or body]

On Mon, Aug 12, 2019, 18:46 Ben Cooksley <bcooksley@kde.org> wrote:

> On Mon, Aug 12, 2019 at 10:37 PM Albert Vaca Cintora
> <albertvaka@gmail.com> wrote:
> >
> > Could we use sysadmin/repo-metadata to know which branch is stable and
> therefore should be protected and trigger the hooks for closing bugs, etc?
>
> Unfortunately that only tells us what the current stable branch is -
> it doesn't let us know what the other (either historical or up and
> coming) stable branches are called.
>

Maybe that is enough? IMO, it makes sense to not consider a bug is closed
until the commit that fixes it has been merged to either master or the
current stable branch.

[Attachment #3 (text/html)]

<div dir="auto"><div>  <br><div class="gmail_quote"><div dir="ltr" \
class="gmail_attr">On Mon, Aug 12, 2019, 18:46 Ben Cooksley &lt;<a \
href="mailto:bcooksley@kde.org">bcooksley@kde.org</a>&gt; \
wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 \
.8ex;border-left:1px #ccc solid;padding-left:1ex">On Mon, Aug 12, 2019 at \
10:37 PM Albert Vaca Cintora<br> &lt;<a href="mailto:albertvaka@gmail.com" \
target="_blank" rel="noreferrer">albertvaka@gmail.com</a>&gt; wrote:<br> \
&gt;<br> &gt; Could we use sysadmin/repo-metadata to know which branch is \
stable and therefore should be protected and trigger the hooks for closing \
bugs, etc?<br> <br>
Unfortunately that only tells us what the current stable branch is -<br>
it doesn&#39;t let us know what the other (either historical or up and<br>
coming) stable branches are called.<br></blockquote></div></div><div \
dir="auto"><br></div><div dir="auto"><span \
style="font-family:sans-serif">Maybe that is enough? IMO, it makes sense to \
not consider a bug is closed until the commit that fixes it has been merged \
to either master or the current stable branch.</span></div></div>



[prev in list] [next in list] [prev in thread] [next in thread]