From: Michael Roth <mdroth@linux.vnet.ibm.com>
To: "Andreas Färber" <afaerber@suse.de>,
"Peter Maydell" <peter.maydell@linaro.org>,
"Paolo Bonzini" <pbonzini@redhat.com>
Cc: Anthony Liguori <anthony@codemonkey.ws>,
KVM devel mailing list <kvm@vger.kernel.org>,
Juan Quintela <quintela@redhat.com>,
qemu list <qemu-devel@nongnu.org>,
Bruce Rogers <brogers@suse.com>,
Christian Borntraeger <borntraeger@de.ibm.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
Anthony Liguori <aliguori@amazon.com>
Subject: Re: [Qemu-devel] KVM call agenda for 2014-04-01
Date: Mon, 31 Mar 2014 14:57:59 -0500 [thread overview]
Message-ID: <20140331195759.22831.40560@loki> (raw)
In-Reply-To: <53397FD5.5050802@suse.de>
Quoting Andreas Färber (2014-03-31 09:46:45)
> Am 31.03.2014 16:32, schrieb Peter Maydell:
> > On 31 March 2014 15:28, Paolo Bonzini <pbonzini@redhat.com> wrote:
> >> I think it would be a good idea to separate the committer and release
> >> manager roles. Peter is providing the community with a wonderful service,
> >> just like you were; putting too much work on his shoulders risks getting us
> >> in the same situation if anything were to affect his ability to provide it.
> >
> > Yes, I strongly agree with this. I think we'll do much better
> > if we can manage to share out responsibilities among a wider
> > group of people.
>
> May I propose Michael Roth, who is already experienced from the N-1
> stable releases?
Sure, I would be willing.
>
> If we can enable him to upload the tarballs created from his tags that
> would also streamline the stable workflow while at it.
Agreed, though I feel a little weird about creating releases for tags that
aren't in the official repo. Would that be acceptable from a community
stand-point? I'm honestly not sure.
Otherwise I think Anthony/Peter would probably still need to process a pull
for stable-y.x branch in advance before we do the tarball/release. Would
still help simplify things a bit though by keeping tasks compartmentalized.
Anthony, Peter: in the past, prior to release, I just sent an email with
a pointer to my github branch with the stable release tagged. Would a proper
pull request (with a for-stable-x.y tag or somesuch) be preferable?
If we opt to align the stable repo updates with the actual release, what kind
of lead time would we need prior to actual release?
>
> Regards,
> Andreas
>
> --
> SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
> GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
next prev parent reply other threads:[~2014-03-31 19:58 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-31 10:40 [Qemu-devel] KVM call agenfda for 2014-04-01 Juan Quintela
2014-03-31 10:51 ` [Qemu-devel] KVM call agenda " Andreas Färber
2014-03-31 12:07 ` Stefan Hajnoczi
2014-03-31 13:21 ` Christian Borntraeger
2014-03-31 13:25 ` Peter Maydell
2014-03-31 14:01 ` Anthony Liguori
2014-03-31 14:28 ` Paolo Bonzini
2014-03-31 14:32 ` Peter Maydell
2014-03-31 14:46 ` Andreas Färber
2014-03-31 15:42 ` Anthony Liguori
2014-03-31 16:58 ` Markus Armbruster
2014-03-31 19:57 ` Michael Roth [this message]
2014-04-01 8:16 ` Peter Maydell
2014-04-01 12:39 ` [Qemu-devel] KVM call agenfda " Juan Quintela
2014-04-10 15:49 ` Alexander Graf
2014-04-10 15:52 ` Peter Maydell
2014-04-10 15:57 ` Alexander Graf
2014-04-10 16:16 ` Stuart Yoder
2014-04-11 7:46 ` Markus Armbruster
2014-04-11 9:17 ` Alexander Graf
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=20140331195759.22831.40560@loki \
--to=mdroth@linux.vnet.ibm.com \
--cc=afaerber@suse.de \
--cc=aliguori@amazon.com \
--cc=anthony@codemonkey.ws \
--cc=borntraeger@de.ibm.com \
--cc=brogers@suse.com \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=stefanha@redhat.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).