Release Status

Richard Purdie

[Cross posted as I think there are two interested parties in this

Things have been a little chaotic recently and I wish they could have
been different. We've just had to make the best of them however and I do
think things are coming together. Things were not helped by the fact I
was travelling last week and distracted by the commitments that

We have branched both OE-Core and Yocto and master is now open for
normal business again. I'm trying to catch up on the patch backlog,
anyone creating pull requests of sets of outstanding changes would help
me a lot there but failing that I'll continue to work through things as
quickly as I can. I've tried to pick up the simpler and more obvious
patches to keep the queue under control.

We're at -rc3 with the rc3 builds having just completed. The builds
themselves were mostly successful (greenest build yet certainly) and I
think the failed tasks are autobuilder issues rather than metadata/build
system ones but we'll be working to confirm that. The QA team will be
testing the result of that build this week.

Feature wise, testing is showing there are issues in some of the
stranger multilib combinations but that standard ones do work. Hob is
showing some issues but many of the bugs we originally found have been
fixed. There are also still a strong stream of general bug fixes coming

We are likely going to run a -rc4 build in two weeks, the week delay
being due to the holiday in China where the Yocto QA team is based. This
means we do slip from the release date we had in mind but this gives us
a little more runway to fix any remaining key issues.

At this point given the problems we've had getting all the combinations
we build to work, I'm reluctant to take more than the bare essential
fixes for -rc4 but we'll see how things look on the rc3 QA report.

I'd urge people to continue fixing bugs. We're seeing the "quality" of
master improving a lot with removal of a ton of QA warnings, unpackaged
files and so forth with bugs being dug into, debugged and resolved and
many good things happening. If there are a load of changes which don't
make the release, its possible we may end up taking those into a point
release. At present the Yocto bug trends are not looking very positive
but I'm optimistic that even if issues are reported, if we do debug them
and have known fixes that is a better position to be in than not having
them available.

I was feeling quite nervous about things but I'm feeling things are more
under control now. Lets hope this is true as we await the -rc3 test
reports! :)



Join to automatically receive all group messages.