Re: [tsc] [qa-build-notification] QA notification for completed autobuilder build (yocto-5.0.rc2)

[Denys Dmytriyenko <denis@denix.org>]

On Thu, Apr 18, 2024 at 11:49:26AM +0100, Richard Purdie wrote:
> On Thu, 2024-04-18 at 10:45 +0000, Ross Burton wrote:
> > On 18 Apr 2024, at 09:11, Richard Purdie <richard.purdie@linuxfoundation.org> wrote:
> > > For the purposes of history, the issue is in curl 8.7.0 and 8.7.1 was
> > > just a single bug fix. There is a fix in git master branch for the curl
> > > issue and curl themselves also have a fix in master as yet unreleased.
> > > I've backported the patch to git for now, we can drop it when we
> > > upgrade things.
> > 
> > As the underlying issue is in curl and has been fixed in master:
> > 
> > https://github.com/curl/curl/commit/721941aadf4adf4f6aeb3f4c0ab489bb89610c36
> > 
> > I think we should apply this instead.  The issue is a curl regression, we just saw it first in git.
> > 
> > I lean towards this being a release blocker and think we should respin.
> 
> Much as I would prefer not to, I agree. 
> 
> We should abandon rc2 and build an rc3. I'd like to keep the
> dunfell/kirkstone builds for after rc3 goes through QA though. We
> should be able to build rc3 quite quickly.

I believe 5.0 is still "within" the schedule, right?

What about dunfell and kirkstone minor releases? I know their builds are being 
delayed by 5.0 taking up AB. But are they already behind the schedule? If not, 
then 5.0 rc3 should definitely get prioritized.

-- 
Denys