Re: GitLab: Default set of status/resolutions/labels for GNOME

--===============3479262494080463571==
Content-Type: multipart/alternative; boundary="089e0826e9cc66a21c055a852310"

--089e0826e9cc66a21c055a852310
Content-Type: text/plain; charset="UTF-8"

On Sun, Oct 1, 2017 at 3:20 PM Carlos Soriano <[email protected]> wrote:

> Hey Philip,
>
> > it was pretty much going to happen unless something went drastically
> wrong
>
> Not sure I would say it with those words, but yes, we are in the same
> situation as it was before and things keep progressing well.
>
> But this has to come with community built-in, and not only I cannot
> control that, but it's also hard to quantify. So I don't really want
> to commit myself into an answer for that as for now, it depends on all
> of you, specially those in the pilot program giving feedback to us and
> the rest of the community. I'll keep doing my best trying to quantify
> the community agreement/satisfaction (+ all the technical part and
> discussion with GitLab people about our priorities, etc. of course).
>
> Hope is clearer now, or at least know why I cannot be clearer :)
>

OK. I have been doing some research and was planning to spend some effort
creating a proper CI pipeline for merge requests and releases after GJS
gets moved over, and I had a momentary panic about whether it would be wise
to spend that time when it's unclear if we're staying with Gitlab.

--089e0826e9cc66a21c055a852310
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_quote"><div dir=3D"ltr">On Sun, Oct 1,=
 2017 at 3:20 PM Carlos Soriano &lt;<a href=3D"mailto:[email protected]">c=
[email protected]</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote"=
 style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">He=
y Philip,<br>
<br>
&gt; it was pretty much going to happen unless something went drastically w=
rong<br>
<br>
Not sure I would say it with those words, but yes, we are in the same<br>
situation as it was before and things keep progressing well.<br>
<br>
But this has to come with community built-in, and not only I cannot<br>
control that, but it&#39;s also hard to quantify. So I don&#39;t really wan=
t<br>
to commit myself into an answer for that as for now, it depends on all<br>
of you, specially those in the pilot program giving feedback to us and<br>
the rest of the community. I&#39;ll keep doing my best trying to quantify<b=
r>
the community agreement/satisfaction (+ all the technical part and<br>
discussion with GitLab people about our priorities, etc. of course).<br>
<br>
Hope is clearer now, or at least know why I cannot be clearer :)<br></block=
quote><div><br></div><div>OK. I have been doing some research and was plann=
ing to spend some effort creating a proper CI pipeline for merge requests a=
nd releases after GJS gets moved over, and I had a momentary panic about wh=
ether it would be wise to spend that time when it&#39;s unclear if we&#39;r=
e staying with Gitlab.</div></div></div>

--089e0826e9cc66a21c055a852310--

--===============3479262494080463571==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
desktop-devel-list mailing list
[email protected]
https://mail.gnome.org/mailman/listinfo/desktop-devel-list
--===============3479262494080463571==--