qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Cédric Le Goater" <clg@redhat.com>
To: "Alex Bennée" <alex.bennee@linaro.org>,
	"Peter Maydell" <peter.maydell@linaro.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: QEMU Summit Minutes 2023
Date: Tue, 28 Nov 2023 18:54:42 +0100	[thread overview]
Message-ID: <ef77ed27-8b95-480e-97da-8e0c53bf3aa1@redhat.com> (raw)
In-Reply-To: <87edgjf2v4.fsf@draig.linaro.org>

On 11/21/23 18:11, Alex Bennée wrote:
> Peter Maydell <peter.maydell@linaro.org> writes:
> 
>> QEMU Summit Minutes 2023
>> ========================
>>
>> As usual, we held a QEMU Summit meeting at KVM Forum.  This is an
>> invite-only meeting for the most active maintainers and submaintainers
>> in the project, and we discuss various project-wide issues, usually
>> process stuff. We then post the minutes of the meeting to the list as
>> a jumping off point for wider discussion and for those who weren't
>> able to attend.
>>
> <snip>
>>
>> Topic 2: Are we happy with the email workflow?
>> ==============================================
>>
>> This was a topic to see if there was any consensus among maintainers
>> about the long-term acceptability of sticking with email for patch
>> submission and review -- in five years' time, if we're still doing it
>> the same way, how would we feel about it?
>>
>> One area where we did get consensus was that now that we're doing CI
>> on gitlab we can change pull requests from maintainers from via-email
>> to gitlab merge requests. This would hopefully mean that instead of
>> the release-manager having to tell gitlab to do a merge and then
>> reporting back the results of any CI failures, the maintainer
>> could directly see the CI results and deal with fixing up failures
>> and resubmitting without involving the release manager. (This
>> may have the disbenefit that there isn't a single person any
>> more who looks at all the CI results and gets a sense of whether
>> particular test cases have pre-existing intermittent failures.)
> 
> If we are keen to start processing merge requests for the 9.0 release we
> really should consider how it is going to work before we open up the
> taps post 8.2-final going out.
>
> Does anyone want to have a go at writing an updated process for
> docs/devel/submitting-a-pull-request.rst (or I guess merge-request) so
> we can discuss it and be ready early in the cycle? Ideally someone who
> already has experience with the workflow with other gitlab hosted
> projects.


Reading the Topic 2 paragraph above, I understand that a maintainer
of a subsystem would be able to merge its '-next' branch in the main
repository when CI is all green. Correct ?

It seems to me that we should also have a group of people approving
the MR.

Thanks,

C.



  reply	other threads:[~2023-11-28 17:55 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-13 13:21 QEMU Summit Minutes 2023 Peter Maydell
2023-08-17  6:13 ` Thomas Huth
2023-11-21 17:11 ` Alex Bennée
2023-11-28 17:54   ` Cédric Le Goater [this message]
2023-11-28 18:05     ` Peter Maydell
2023-11-28 18:09       ` Daniel P. Berrangé
2023-11-28 18:06     ` Daniel P. Berrangé
2023-11-29 14:21       ` Philippe Mathieu-Daudé
2023-11-29 15:45         ` Warner Losh
2023-11-29 15:47         ` Stefan Hajnoczi
2023-11-29 15:53           ` Stefan Hajnoczi
2023-11-29 16:46             ` Daniel P. Berrangé
2023-11-29 16:49               ` Stefan Hajnoczi
2023-11-29 16:57             ` Alex Bennée
2023-11-29 18:24               ` Stefan Hajnoczi
2023-11-29 15:50       ` Warner Losh
2023-11-29 16:49         ` Daniel P. Berrangé
2023-11-29 19:41           ` Peter Maydell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ef77ed27-8b95-480e-97da-8e0c53bf3aa1@redhat.com \
    --to=clg@redhat.com \
    --cc=alex.bennee@linaro.org \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).