From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Claudio Fontana <cfontana@suse.de>
Cc: "Juan Quintela" <quintela@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Peter Maydell" <peter.maydell@linaro.org>,
"Peter Xu" <peterx@redhat.com>, "Fabiano Rosas" <farosas@suse.de>,
"Steve Sistare" <steven.sistare@oracle.com>,
qemu-devel@nongnu.org,
"Philippe Mathieu-Daudé" <philmd@linaro.org>
Subject: Re: migration maintenance, governance [Was: Re: [PATCH V4 0/2] migration file URI]
Date: Wed, 27 Sep 2023 15:31:28 +0100 [thread overview]
Message-ID: <ZRQ8wOhTNDEL3suv@redhat.com> (raw)
In-Reply-To: <9833202a-8060-1e81-208e-4e240279c298@suse.de>
On Wed, Sep 27, 2023 at 03:14:29PM +0200, Claudio Fontana wrote:
> On 9/13/23 15:00, Claudio Fontana wrote:
> > On 8/30/23 15:09, Claudio Fontana wrote:
> >> On 8/22/23 15:25, Philippe Mathieu-Daudé wrote:
> >>> Hi Claudio,
> >>>
> >>> On 22/8/23 14:00, Claudio Fontana wrote:
> >>>> Hello,
> >>>>
> >>>> this series is all reviewed,
> >>>>
> >>>> and is needed as a precondition for further work to improve dramatically the performance of virsh save, virsh restore
> >>>> when migrating to disk, can it be merged?
> >>>
> >>> $ ./scripts/get_maintainer.pl -f migration/meson.build
> >>> Juan Quintela <quintela@redhat.com> (maintainer:Migration)
> >>> Peter Xu <peterx@redhat.com> (reviewer:Migration)
> >>> Leonardo Bras <leobras@redhat.com> (reviewer:Migration)
> >>> qemu-devel@nongnu.org (open list:All patches CC here)
> >>>
> >>> One maintainer, one single point of failure. When the
> >>> maintainer is busy or offline (vacations?) then everybody
> >>> is stuck.
> >>>
> >>> This is usually solved by adding co-maintainers.
> >>>
> >>> Juan, would you accept having co-maintainers helping you
> >>> dealing with the merge process? I'm not volunteering, but
> >>> this can be a good opportunity to make a formal request to
> >>> the community.
> >>
> >> I would like to highlight to the QEMU community here how important this is for SUSE,
> >>
> >> to see progress for all the series in the migration area that are currently still waiting and competing for attention.
> >>
> >> The specific features and improvements we are developing or helping to review are a priority for us,
> >> and we are concerned about the rate of progress with the existing governance processes.
> >>
> >> Fabiano is investing a lot of his attention to this area, with features, bugfixes and reviews,
> >> but of course it is up to the community as a whole to address the issue so that reviewed work is merged.
> >>
> >> My attempt here is to make sure that it is recognized as a problem, so it can be hopefully be addressed by the community in a timely fashion,
> >> and we can all benefit from the already developed and reviewed work that is pending.
> >>
> >
> > Hi Juan, any comments? Would additional help for co-maintenance of live migration help?
> > How can we make things proceed?
> >
> > From our (SUSE) side we are willing to help as much as we can, and all options are open,
> > whatever it takes to get the multiple series currently waiting to flow again.
> >
> > Thanks,
> >
> > Claudio
>
> Hi any news here?
>
> We continue to see the migration area of QEMU as basically blocked;
>
> there are a number of reviewed series out and little progress in merging them,
> as well as a number of improvements not posted to the list at all due to the situation being completely bottlenecked.
>
> Would a co-maintenance of migration/ from Fabiano be an option?
>
> Should we organize a call to discuss this if the mailing list does not suffice to discuss this topic?
FWIW, in response to your previous mail, I had suggested to Peter Xu in
private that he would make a good candidate of co-maintainer for migration,
given he is already a nominated reviewer and has been actively reviewing
migration patches for a long while.
Migration did have 2 maintainers until earlier in this year when David
Gilbert moved on to other things, and I think we can all see that this
has had an unfortunate impact on productivity in the migration subsystem
that needs to be solved.
With regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
prev parent reply other threads:[~2023-09-27 14:32 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-30 14:25 [PATCH V4 0/2] migration file URI Steve Sistare
2023-06-30 14:25 ` [PATCH V4 1/2] migration: " Steve Sistare
2023-08-30 13:16 ` Daniel P. Berrangé
2023-08-30 14:15 ` Steven Sistare
2023-09-08 10:52 ` Daniel P. Berrangé
2023-09-08 14:23 ` Steven Sistare
2023-06-30 14:25 ` [PATCH V4 2/2] migration: file URI offset Steve Sistare
2023-07-13 21:26 ` [PATCH V4 0/2] migration file URI Michael Galaxy
2023-08-22 12:00 ` Claudio Fontana
2023-08-22 13:25 ` Philippe Mathieu-Daudé
2023-08-30 13:09 ` Claudio Fontana
2023-09-13 13:00 ` Claudio Fontana
2023-09-27 13:14 ` migration maintenance, governance [Was: Re: [PATCH V4 0/2] migration file URI] Claudio Fontana
2023-09-27 13:56 ` Peter Xu
2023-09-27 14:36 ` Daniel P. Berrangé
2023-09-27 15:15 ` Peter Xu
2023-09-27 14:31 ` Daniel P. Berrangé [this message]
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=ZRQ8wOhTNDEL3suv@redhat.com \
--to=berrange@redhat.com \
--cc=cfontana@suse.de \
--cc=farosas@suse.de \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=peterx@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=steven.sistare@oracle.com \
/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).