Re: QEMU stable 7.2.1

[Michael Roth]

On Wed, Apr 05, 2023 at 05:16:33PM +0300, Michael Tokarev wrote:
> 05.04.2023 16:58, Michael Roth wrote:
> > On Wed, Apr 05, 2023 at 02:54:47PM +0300, Michael Tokarev wrote:
> > > So let it be, with a delay of about a week.
> > > 
> > > Since no one from the qemu team replied to my final-release steps, I'm
> > > making it available on my site instead:
> > > 
> > >    http://www.corpit.ru/mjt/qemu/qemu-7.2.1.tar.xz
> > >    http://www.corpit.ru/mjt/qemu/qemu-7.2.1.tar.xz.sig - signed with my 
> > > GPG key
> > >    http://www.corpit.ru/mjt/qemu/qemu-7.2.1.diff - whole difference from 
> > > 7.2.0.
> > > 
> > > The tag (v7.2.1) is in the main qemu repository.
> > 
> > Hi Michael,
> > 
> > Thanks for handling this release!
> > 
> > Somehow I missed your final steps email, but for future releases I would
> > recommend going ahead and tagging your release (also signed with your GPG
> > key) in your local tree once you've got everything ready, and then sending
> > me an email to directly so I can push that to gitlab and then handle
> > creating the tarball and publish it with my GPG key. That's basically what
> > we do for the normal QEMU releases as well.
> > 
> > Then once you get your accounts set up by gitlab/qemu.org admins you can
> > handle the tag-pushing/tarball-uploading on your end. Would be good to
> > have someone else involved with that process so we have some redundancy
> > just in case.
> 
> Thank you for the reply!
> 
> I'm not sure I follow you here. I already pushed v7.2.1 tag and stable-7.2
> branch to gitlab/qemu. The branch has been there for quite some time.

Oh! Nice, didn't realize you were set up there already. Just noticed the
7.2.1 tag when pulling down 8.0.0-rc3.

That also helped me notice that your reply here got quarantined by my email
server, along with a number of your previous emails relating to stable, so
that explains how those slipped by (the ones that hit the mailing list
still show up if I'm looking in the right place).

I'll keep a better eye out for this in the future and try to reach an
understanding with this advanced AI technology that treats straight-forward
direct replies to my emails as spam for inexplicable reasons.

> 
> Should I avoid tagging/pushing for the future or is it okay to do that?

Nope, that's fine. Just ignore my comments regarding git, everything seems
to be good on that end.

One thing I forgot to mention previously is updating the wiki with the
release schedule once you have an idea of when you plan to push your tags.
E.g.:

  https://wiki.qemu.org/Planning/7.2

I usually set the date once I have the initial staging ready and get
ready to send out the "patch round-up" with expected freeze/release
dates. Might be good to email me directly or Cc: me on related
announcements around that time so I can make sure I'm around.

> 
> For the tarballs, it's definitely better to follow the established practice,
> I published the generated tarball on my site just as a last-resort, so that
> it ends up *somewhere*. It should be prepared the same way as other releases
> has been made, including the .bz2 version.
> 
> If that's okay with you, feel free to re-create the tarball from v7.2.1
> tag, and compress the tarball with whatever compressors usually used by
> the qemu team.  It's the way to go.

Ok, sure, I'll go ahead and re-publish 7.2.1 tarball a bit later today.

We can stick with this approach until you're all set up for uploading.

-Mike

> 
> Thanks,
> 
> /mjt
>