On Thu, 2018-06-07 at 13:33 -0500, Michael Catanzaro wrote:
> So there were failures on master today, but no emails reached the
> list... why did they get rejected this time?
https://mail.gnome.org/mailman/admindb/release-team says there are no
pending requests, and I did not get any mail
So there were failures on master today, but no emails reached the
list... why did they get rejected this time?
___
release-team@gnome.org
https://mail.gnome.org/mailman/listinfo/release-team
Release-team lurker? Do NOT participate in discussions.
I'm worried that it's sending emails when Abderrahim's sidebranch
pipelines fail. Could you check if that's true, Andre?
We really only want it to send mail when the master branch pipeline
fails, so I will turn this off if that's the case. GitLab. :/
Michael
On Sun, 2018-06-03 at 19:38 +0200, Andre Klapper wrote:
> I've added gitlab-issues@ to the "Accepts" sender filter.
That did not help because "Message has implicit destination", still. I
now disabled "require_explicit_destination" on
On Sun, 2018-06-03 at 12:02 -0500, mcatanz...@gnome.org wrote:
> On Sun, Jun 3, 2018 at 11:14 AM, Andre Klapper wrote:
> > Shall we allow them by default or will this be too much noise?
>
> The goal is to use release-team@ to assess whether it will be too much
> noise for desktop-devel@. I
On Sun, Jun 3, 2018 at 11:14 AM, Andre Klapper wrote:
Shall we allow them by default or will this be too much noise?
The goal is to use release-team@ to assess whether it will be too much
noise for desktop-devel@. I would allow them for release-team@, for
sure, because the entire release
There are a bunch of posts in the moderation queue, such as:
> As list administrator, your authorization is requested for the
> following mailing list posting:
>
> List:release-team@
> From:gitlab-issues@
> Subject: gnome-build-meta | Pipeline #14101 has failed for master | 201d1eca
>