qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: Michael Tokarev <mjt@tls.msk.ru>,
	QEMU Developers <qemu-devel@nongnu.org>,
	Michael Roth <michael.roth@amd.com>
Cc: Peter Maydell <peter.maydell@linaro.org>, qemu-stable@nongnu.org
Subject: Re: stable releases
Date: Mon, 6 Mar 2023 09:57:58 +0100	[thread overview]
Message-ID: <0d2a9e13-850e-d140-d63e-a940148bdccc@redhat.com> (raw)
In-Reply-To: <69963eba-d001-150c-71d4-b2b23bfed4d1@msgid.tls.msk.ru>

On 05/03/2023 11.27, Michael Tokarev wrote:
> Hi!
> 
> For a few qemu major releases already, we did not have any stable minor 
> releases.
> I'd love to change that, in order to consolidate efforts and to make better
> software in the end.  But I need some (hopefully minor) help here.
> 
> I collected changes from qemu/master which apparently should go to -stable.
> Published at git://isrv.corpit.ru/qemu.git , branch stable-7.2-staging
> (probably should publish it on github or gitlab).
> This contains stuff which I use on Debian in qemu package, which is based
> on 7.2 version now.  The last 18 patches are not in Debian package yet,
> going to push it today or tomorrow.
> 
> If nothing, this can be used as a base for actual 7.2.1 stable release,
> maybe with more changes added (or some changes removed).
> 
> The help which I need is to be able to run some wider testing. Debian is
> a relatively good testbed, and it is used by qemu already in terms of
> bullseye-backports to run other tests, so it should be good, but I'd
> love to have wider coverage still. Maybe some CI stuff which qemu has
> for master, if not only just before actual release.

I'd suggest to get a gitlab.com account, and fork the qemu repository there. 
Then you can run the CI on your own by pushing your patch to your forked 
repository.

You can also get some test additional coverage by running the avocado tests 
with "make check-avocado" ... but beware that this downloads quite some 
hundreds of MBs from the internet. And some tests are known to fail, so it's 
maybe best to run them on the plain 7.2.0 tag first to see what works for 
you and what does not work properly.

> And as usual, this needs help in picking up changes which should go to
> stable. But this is something which is always needed anyway.
> 
> Let's resurrect qemu-stable :)

Please make sure to CC: qemu-stable and Michael Roth - I hope he can give 
some directions for this effort.

  Thomas



  reply	other threads:[~2023-03-06  8:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-05 10:27 stable releases Michael Tokarev
2023-03-06  8:57 ` Thomas Huth [this message]
2023-03-08  2:59   ` Michael Roth via

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=0d2a9e13-850e-d140-d63e-a940148bdccc@redhat.com \
    --to=thuth@redhat.com \
    --cc=michael.roth@amd.com \
    --cc=mjt@tls.msk.ru \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-stable@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).