Re: [BuildStream] Gitlab Merge Trains

[Sander Striker <s striker striker nl>]

Hi,

I do not know what "a broad consensus on IRC" means.  Consensus between who?  I know for a fact that part of the community cannot easily be on IRC and therefor isn't.

On the topic of Marge Bot and switching to a more general feature, I think that is fine, with appropriate notice.  Maybe also with a more catchy subject line like "Retiring Marge-Bot, Workflow Change".

Cheers,

Sander

On Tue, Jul 23, 2019 at 5:06 PM Alexandru Fazakas via buildstream-list <buildstream-list gnome org> wrote:

Hi all,

Due to a broad consensus on IRC, with Gitlab's addition of Merge Trains[1]
we are moving away from using Marge Bot. The changes to the code base
itself are not massive. We're no longer running the usual tests (e.g. everything
other than overnight ones) on master, as they would have already been ran
on their branch previously.

Regarding developer work flow: instead of assigning Marge Bot to an accepted
MR, we should just add the MR to a merge train (or start one should none be
already running), as explained in the documentation below.

This change should make accepting and merging multiple MR's at once
easier to do and manage with Gitlab's support.

Regards,
Alex

[1] Gitlab merge trains

_______________________________________________
buildstream-list mailing list
buildstream-list gnome org
https://mail.gnome.org/mailman/listinfo/buildstream-list