[Mesa-dev] Thoughts after hitting 100 merge requests?

[Juan A. Suarez Romero]

On Fri, 2019-01-25 at 13:26 -0800, Eric Anholt wrote:
> Rob Clark <robdclark at gmail.com> writes:
> 
> > I guess as discovered with
> > https://gitlab.freedesktop.org/mesa/mesa/merge_requests/47 maybe we
> > should wait to turn on merging MRs via web until we have at least some
> > basic build-test CI wired up.. the downside is slower 'maintainer'
> > response (if I am working on some long running branch I tend to
> > postpone pushing changes from others until I am in a good state to
> > rebase, but at least when I merge things via cmdline I do a build test
> > and sanity test on at at least one driver ;-))
> 
> We should be days, not weeks, away from having build-test CI wired up.
> I actually thought Igalia was supposed to be working on it again
> already, but then Eric Engestrom started working on a new variation, so
> I'm not sure what's going on.
> 

Yes, I had the plan to update and create a MR with the GitLab CI proposal that I
had sent to mailing list at the beginning of the month, but for personal issues
I completely forgot about it. I'm really really sorry about it.

I don't know how much late I'm are to propose it. In any case, I've everything
ready to create a MR. But as it would be impolite impolite to do it after Eric
created one, I've left a comment in Eric's MR#146 with the proposal, explaining
it.

If Eric and others are fine, I can create a MR too.

	J.A.

> I'm skeptical that we need to do an MR policy change given that
> build-breakage and especially unit-test-breakage has been a recurring
> issue in the absence of CI, even before MRs.
> _______________________________________________
> mesa-dev mailing list
> mesa-dev at lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/mesa-dev