Bug 14276

Summary:	dunfell LTS branch incorrectly updated to 3.2 gatesgarth
Product:	[Build System, Metadata & Runtime] OE-Core	Reporter:	Doug Chapman <doug.chapman>
Component:	configuration	Assignee:	Unassigned <unassigned>
Status:	RESOLVED NOTABUG	QA Contact:
Severity:	major
Priority:	Undecided
Version:	3.1.7
Target Milestone:	---
Hardware:	x86
OS:	Multiple
Whiteboard:
OS type for building Yocto:	---	Type of Regression:	---
Verified:		Documentation change:	Don't know

Description Doug Chapman 2021-03-02 19:20:27 UTC

My intention is to use the dunfell release since it is the LTS release and also I need the meta-ti layer that does not yet support gatesgarth.  However, the dunfell branch in git is no longer dunfell, it was updated to gatesgarth.

The change came in this commit:

commit b7591c86c159e031763ec5906b879ce6b179342d
Author: Richard Purdie <richard.purdie@linuxfoundation.org>
Date:   Tue Oct 20 11:21:40 2020 +0100

    poky.conf: Bump version for 3.2 gatesgarth release
    
    (From meta-yocto rev: 269f81c2b2ac64219c65953bc56bd41317a8db0f)
    
    Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>


I believe this commit was pushed to the wrong branch, it should have just been on the gatesgarth branch since dunfell is supposed to be LTS supported for 2 years.

Comment 1 Doug Chapman 2021-03-02 19:33:00 UTC

oops, my bad.  Had messed up my git branches...