Re: Status of stable release effort ?

["Daniel P. Berrangé" <berrange@redhat.com>]

On Tue, Aug 03, 2021 at 09:31:44AM -0500, Michael Roth wrote:
> Quoting Daniel P. Berrangé (2021-07-26 05:13:41)
> > We are currently in the final lead up to shipping the 6.1.0 release
> > 
> > AFAICT from git tags, the latest stable release was 5.0.1 in Sep 2020
> > 
> >    https://gitlab.com/qemu-project/qemu/-/tags
> > 
> > There have been many patches sent to qemu-stable each month e.g.
> > 
> >   https://lists.nongnu.org/archive/html/qemu-stable/2021-06/threads.html
> > 
> > but no 5.1.1, 5.2.1 or 6.0.1 releases IIUC
> > 
> > Is QEMU stable still an active effort that we need to CC patches to ?
> 
> Hi Daniel,
> 
> Long story short: I tossed away my test setup when I switched employers
> last year with plans to make better use of the new gitlab infrastructure
> and make it easier to swap in different maintainers as-needed, sort of
> like what Peter has been working on for qemu mainline. Things ramped up
> a bit faster than expected here however and it's been on my queue ever
> since.
> 
> My plan has been to resume regular stable releases starting with 6.0.1
> within the next few weeks, but still need to take a good hard look at the
> testing situation and how we can make the process more resilient. I'd
> hoped to find time to dig into laying out an overall test plan a bit more
> before responding but will find some cycles to do so as I work on getting
> the 6.0.1 release together.
> 
> I apologize to anyone who spent time curating patches for
> qemu-stable@nongu.org, the ones targetted for anything prior to 6.0.1 likely
> won't make a stable release, but if there's something I should reconsider
> please let me know. And please don't let my poor handling of things affect
> the overall process, there have been others in the community that have shown
> interest helping with stable in the past, but the testing situation has always
> made it difficult move forward with things, so if that can be improved in that
> regard then I think we could expect the process improve.

For 6.0.1 you're still going to be lacking the gitlab CI custom runner
config that Peter has just started using for testing for non-x86 arch
coverage.

It will at least have the x86 coverage using shared runners though
which is better than nothing.

The custom runner config invokes jobs when pushing to 'qemu-project'
gitlab namespace (ie not user forks), if using a branch with a name
prefix 'staging'. So from 6.1.1 onwards if you push to (for example)
'staging-stable' branch that'll trigger the same set of GitLab CI
jobs that Peter runs for the master branch.


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 :|