Yocto Project - User contributions [en]

User talk:Aurelien DESBRIERES

2026-04-13T06:35:42Z

MichaelHalstead: Welcome!

'''Welcome to ''Yocto Project''!'''
We hope you will contribute much and well.
You will probably want to read the [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents help pages].
Again, welcome and have fun! [[User:MichaelHalstead|MichaelHalstead]] ([[User talk:MichaelHalstead|talk]]) 06:35, 13 April 2026 (UTC)

User:Aurelien DESBRIERES

2026-04-13T06:35:42Z

MichaelHalstead: Creating user page for new user.

I like Rolling release and I like embedded things :)

Layerindex

2025-06-27T18:38:08Z

MichaelHalstead: Add directions for creating new branches on layerindex.

= How to Add a New Branch to layers.openembedded.org =

This document outlines the steps to add a new branch and its associated releases and milestones to layers.openembedded.org.

'''Note:''' Throughout this document, the version "5.3" is used as an example. When following these instructions, please replace "5.3" with the actual current version you are working with.

== Procedure ==

# '''Log In:''' Ensure you are logged into the layers.openembedded.org administration interface.
# '''Add a Branch:'''
#* Navigate to [https://layers.openembedded.org/admin/layerindex/branch/ https://layers.openembedded.org/admin/layerindex/branch/].
#* Click "Add branch" and fill in the necessary details for the new branch.
# '''Add Releases:'''
#* Go to [https://layers.openembedded.org/admin/rrs/release/ https://layers.openembedded.org/admin/rrs/release/].
#* Add four new releases, one for each of the following layers, associating them with the '''5.3''' version:
#** <code>meta-virtualization - 5.3</code>
#** <code>meta-openembedded - 5.3</code>
#** <code>meta-intel - 5.3</code>
#** <code>OE-Core - 5.3</code>
#* '''Populate Dates:''' Use the following resources to accurately populate the release dates:
#** [https://wiki.yoctoproject.org/wiki/Releases#Release_Activity Yocto Project Wiki: Release Activity]
#** [https://wiki.yoctoproject.org/wiki/Weekly_Status Yocto Project Wiki: Weekly Status]
#** Relevant Git tags for each project.
# '''Verify Milestones:'''
#* Visit [https://layers.openembedded.org/admin/rrs/milestone/ https://layers.openembedded.org/admin/rrs/milestone/].
#* Verify that all seven required milestones exist for the '''5.3''' version:
#** <code>meta-virtualization: 5.3 Default</code>
#** <code>meta-openembedded: 5.3 Default</code>
#** <code>meta-intel: 5.3 Default</code>
#** <code>OE-Core: 5.3 M4</code>
#** <code>OE-Core: 5.3 M3</code>
#** <code>OE-Core: 5.3 M2</code>
#** <code>OE-Core: 5.3 M1</code>

Releases

2025-05-07T23:58:20Z

MichaelHalstead: /* Release Activity */ color code

== Release Activity==

See also [https://docs.yoctoproject.org/dev/_images/releases.svg a graphical release timeline].

Releases can be downloaded at https://www.yoctoproject.org/software-overview/downloads/

{| class="wikitable" border="2"
!Codename
!Yocto Project Version
!Release Date
!Current Version
!Support Level
!Poky Version
!BitBake branch
! Maintainer
!Notes
|-
|Wrynose
|6.0
| April 2026
|
|Future
|N/A
|2.16
|Richard Purdie <richard.purdie@linuxfoundation.org>
|
|-
|Whinlatter
|5.3
| October 2025
|
|Future
|N/A
|2.14
|Richard Purdie <richard.purdie@linuxfoundation.org>
|[[Recipe_Versions|Recipe versions]]
|-
|Walnascar (aka Walna)
|5.2
| April 2025
|
|Support for 7 months (until November 2025)
|N/A
|2.12
|Richard Purdie <richard.purdie@linuxfoundation.org>
|[[Recipe_Versions|Recipe versions]]
|-
|-style="color: slategray;"
|Styhead (like 'try head')
|5.1
| October 2024
|5.1.4 (April 2025)
|EOL
|N/A
|2.10
|Steve Sakoman <steve@sakoman.com>
|
|-
|Scarthgap
|5.0
| April 2024
| 5.0.9 (May 2025)
|Long Term Support (until April 2028)
|N/A
|2.8
|Steve Sakoman <steve@sakoman.com>
|[[Recipe_Versions|Recipe versions]]
|-
|-style="color: slategray;"
|Nanbield (like 'man field')
|4.3
| November 2023
| 4.3.4 (April 2024)
| EOL
|N/A
|2.6
|Steve Sakoman <steve@sakoman.com>
|- style="color: slategray;"
|Mickledore
|4.2
| May 2023
| 4.2.4 (December 2023)
| EOL
|N/A
|2.4
|Steve Sakoman <steve@sakoman.com>
|-style="color: slategray;"
|Langdale
|4.1
| October 2022
| 4.1.4 (May 2023)
| EOL
|N/A
|2.2
|Steve Sakoman <steve@sakoman.com>
|-
|Kirkstone (like 'kirk stun')
|4.0
|May 2022
|4.0.26 (April 2025)
|Long Term Support (Apr. 2026¹)
|N/A
|2.0
|Steve Sakoman <steve@sakoman.com>
|-
|-style="color: slategray;"
|Honister
|3.4
|October 2021
|3.4.4 (May 2022)
|EOL
|N/A
|1.52
|Anuj Mittal <anuj.mittal@intel.com>
|-
|-style="color: slategray;"
|Hardknott
|3.3
|April 2021
|3.3.6 (April 2022)
|EOL
|N/A
|1.50
|Anuj Mittal <anuj.mittal@intel.com>
|-
|-style="color: slategray;"
|Gatesgarth
|3.2
|Oct 2020
|3.2.4 (May 2021)
|EOL
|N/A
|1.48
|Anuj Mittal <anuj.mittal@intel.com>
|-
|-style="color: slategray;"
|Dunfell
|3.1
|April 2020
|3.1.33 (May 2024)
| EOL - LTS¹
|23.0
|1.46
|Steve Sakoman <steve@sakoman.com>
|-style="color: slategray;"
|Zeus
|3.0
|October 2019
|3.0.4 (August 2020)
|EOL
|22.0.3
|1.44
| Anuj/Armin
|-style="color: slategray;"
|Warrior
|2.7
|April 2019
|2.7.4 (June 2020)
|EOL
|21.0
|1.42
|Armin Kuster <akuster808@gmail.com>
|-style="color: slategray;"
|Thud
|2.6
|Nov 2018
|2.6.4 (October 2019)
|EOL
|20.0
|1.40
| Armin Kuster <akuster808@gmail.com>
|-style="color: slategray;"
|Sumo
|2.5
|April 2018
|2.5.3 (April 2019)
|EOL
|19.0
|1.38
| Armin Kuster <akuster808@gmail.com>
|-style="color: slategray;"
|Rocko
|2.4
|Oct 2017
|2.4.4 (November 2018)
|EOL
|18.0
|1.36
| Armin Kuster <akuster808@gmail.com>
|-style="color: slategray;"
|Pyro
|2.3
|May 2017
|2.3.4 (July 2018)
|EOL
|17.0
|1.34
| Armin Kuster <akuster808@gmail.com>
|-style="color: slategray;"
|Morty
|2.2
|Nov 2016
|2.2.4 (July 2018)
|EOL
|16.0
|1.32
| Armin Kuster <akuster808@gmail.com>
|-style="color: slategray;"
|Krogoth
|2.1
|Apr 2016
|2.1.3 (July 2017)
|EOL
|15.0
|1.30
| Armin Kuster <akuster808@gmail.com>
|-style="color: slategray;"
|Jethro
|2.0
|Nov 2015
|2.0.3 (January 2017)
|EOL
|14.0
|1.28
|Robert Yang <liezhi.yang@windriver.com>
|-style="color: slategray;"
|Fido
|1.8
|Apr 2015
|1.8.2
|EOL
|13.0
|1.26
|Joshua Lock <joshua.g.lock@intel.com>
|-style="color: slategray;"
|Dizzy
|1.7
|Oct 2014
|1.7.3
|EOL
|12.0
|1.24
| Armin Kuster <akuster808@gmail.com>
|-style="color: slategray;"
|Daisy
|1.6
|Apr 2014
|1.6.3
|EOL
|11.0
|1.22
| Saul Wold <sgw@linux.intel.com>
|-style="color: slategray;"
|Dora
|1.5
|Oct 2013
|1.5.4
|EOL
|10.0
|1.20
| Robert Yang <liezhi.yang@windriver.com>
|-style="color: slategray;"
|Dylan
|1.4
|Apr 2013
|1.4.3
|EOL
|9.0
|1.18
| Paul Eggleton <paul.eggleton@linux.intel.com>
|-style="color: slategray;"
|Danny
|1.3
|Oct 2012
|1.3.2
|EOL
|8.0
|1.16
|Ross Burton <ross.burton@intel.com>
|-style="color: slategray;"
|Denzil
|1.2
|Apr 2012
|1.2.2
|EOL
|7.0
|1.15
|-style="color: slategray;"
|Edison
|1.1
|Oct 2011
|1.1.2
|EOL
|6.0
|1.13
|-style="color: slategray;"
|Bernard
|1.0
|Apr 2011
|1.0.2
|EOL
|5.0
|1.11
|-style="color: slategray;"
|Laverne
|0.9
|Oct 2010
|
|
|4.0
|1.11
|-style="color: slategray;"
|Green
|N/A
|11 June 2010
|
|
|3.3
|
|-style="color: slategray;"
|Purple
|N/A
|15 Dec 2009
|
|
|3.2
|
|-style="color: slategray;"
|Pinky
|N/A
|12 Nov 2009
|
|
|3.1
|
|-style="color: slategray;"
|Blinky
|N/A
|1 Aug 2007
|
|
|3.0
|
|-style="color: slategray;"
|Clyde
|N/A
|19 Jan 2007
|
|
|2.0
|
|-style="color: slategray;"
|Inky
|N/A
|10 Feb 2006
|
|
|1.0
|
|}

'''Note:''' see also [[Stable Release and LTS]], [[Linux Yocto]], [[Planning]] and [[Release Feature Table]] pages. EOL means some community support on email lists but no commit updates in the repos. There is also OS Vendor support for some Yocto EOL releases.

¹ The 3.1 series and 4.0 were originally planned for two years but extended to four. Future LTS releases are planned for 4 years.

== Releases Links==
{| class="wikitable" border="2"
| align="center" style="background:#f0f0f0;"|'''Yocto Project Release'''
| align="center" style="background:#f0f0f0;"|'''Code Name'''
| align="center" style="background:#f0f0f0;"|'''Poky version'''
| align="center" style="background:#f0f0f0;"|'''Maintainer'''
| align="center" style="background:#f0f0f0;"|'''Features'''
| align="center" style="background:#f0f0f0;"|'''Schedule'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''QA Test Plan'''
| align="center" style="background:#f0f0f0;"|'''QA Test Report'''
| align="center" style="background:#f0f0f0;"|'''Release notes'''

|-valign="top"
| Yocto Project 3.4
| Honister
| 26.0
| Anuj Mittal
| [[Yocto_3.4_Features]]
| [[Yocto_3.4_Schedule]]
| [[Yocto_Project_v3.4_Status]]
| [[Yocto_Project_3.4_Release_Test_Plan | Yocto_3.4_Overall_Test_Plan]]
| [[Yocto_Project_3.4_Release_Test_Plan#Execution_History | 3.4 qa run history]]
| [https://lists.yoctoproject.org/g/yocto-announce/message/229 3.4 release notes]
|-
| Yocto Project 3.3
| Hardknott
| 25.0
| Anuj Mittal
| [[Yocto_3.3_Features]]
| [[Yocto_3.3_Schedule]]
| [[Yocto_Project_v3.3_Status]]
| [[Yocto_Project_3.3_Release_Test_Plan | Yocto_3.3_Overall_Test_Plan]]
| [[Yocto_Project_3.3_Release_Test_Plan#Execution_History | 3.3 qa run history]]
| [https://lists.yoctoproject.org/g/yocto-announce/message/215 3.3 release notes]
|-
| Yocto Project 3.2
| Gatesgarth
| 24.0
| Anuj Mittal
| [[Yocto_3.2_Features]]
| [[Yocto_3.2_Schedule]]
| [[Yocto_Project_v3.2_Status]]
| [[Yocto_Project_3.2_Release_Test_Plan | Yocto_3.2_Overall_Test_Plan]]
| [[Yocto_Project_3.2_Release_Test_Plan#Execution_History | 3.2 qa run history]]
| [https://lists.yoctoproject.org/g/yocto/message/51262 3.2 release notes]
|-
|-valign="top"
| Yocto Project 3.1
| Dunfell
| 23.0
| Steve Sakoman
| [[Yocto_3.1_Features]]
| [[Yocto_3.1_Schedule]]
| [[Yocto_Project_v3.1_Status]]
| [[Yocto_Project_3.1_Release_Test_Plan | Yocto_3.1_Overall_Test_Plan]]
| [[Yocto_Project_3.1_Release_Test_Plan#Execution_History | 3.1 qa run history]]
| [https://lists.yoctoproject.org/g/yocto/message/49201 3.1 release notes]
|-

|-valign="top"
| Yocto Project 3.0
| Zeus
| 22.0
| Armin Kuster/Anuj Mittal
| [[Yocto_2.8_Features]]
| [[Yocto_2.8_Schedule]]
| [[Yocto_Project_v2.8_Status]]
| [[Yocto_Project_2.8_Release_Test_Plan | Yocto_2.8_Overall_Test_Plan]]
| [[Yocto_Project_2.8_Release_Test_Plan#Execution_History | 2.8 qa run history]]
| [https://lists.yoctoproject.org/pipermail/yocto/2019-October/047111.html 3.0 release notes]
|-
|-valign="top"
| Yocto Project 2.7
| Warrior
| 21.0
| Community
| [[Yocto_2.7_Features]]
| [[Yocto_2.7_Schedule]]
| [[Yocto_Project_v2.7_Status]]
| [[Yocto_Project_2.7_Release_Test_Plan | Yocto_2.7_Overall_Test_Plan]]
| [[Yocto_Project_2.7_Release_Test_Plan#Execution_History | 2.7 qa run history]]
| [https://lists.yoctoproject.org/pipermail/yocto/2019-May/045028.html 2.7 release notes]
|-
|-valign="top"
| Yocto Project 2.6
| Thud
| 20.0
| Community
| [[Yocto_2.6_Features]]
| [[Yocto_2.6_Schedule]]
| [[Yocto_Project_v2.6_Status]]
| [[Yocto_Project_2.6_Release_Test_Plan | Yocto_2.6_Overall_Test_Plan]]
| [[Yocto_Project_2.6_Release_Test_Plan#Execution_History | 2.6 qa run history]]
| [https://lists.yoctoproject.org/pipermail/yocto-announce/2018-November/000147.html 2.6 release notes]
|-
|-valign="top"
| Yocto Project 2.5
| Sumo
| 19.0
| Community
| [[Yocto_2.5_Features]]
| [[Yocto_2.5_Schedule]]
| [[Yocto_Project_v2.5_Status]]
| [[Yocto_Project_2.5_Release_Test_Plan | Yocto_2.5_Overall_Test_Plan]]
| [[Yocto_Project_2.5_Release_Test_Plan#Execution_History | 2.5 qa run history]]
| [https://lists.yoctoproject.org/pipermail/yocto-announce/2018-May/000136.html 2.5 release notes]
|-
|-valign="top"
| Yocto Project 2.4
| Rocko
| 18.0
| Community
| [[Yocto_2.4_Features]]
| [[Yocto_2.4_Schedule]]
| [[Yocto_Project_v2.4_Status]]
| [[Yocto_Project_2.4_Release_Test_Plan | Yocto_2.4_Overall_Test_Plan]]
| [[Yocto_Project_2.4_Release_Test_Plan#Execution_History | 2.4 qa run history]]
| [https://lists.yoctoproject.org/pipermail/yocto-announce/2017-October/000125.html 2.4 release notes]
|-
|-valign="top"
| Yocto Project 2.3
| Pyro
| 17.0
| Community
| [[Yocto_2.3_Features]]
| [[Yocto_2.3_Schedule]]
| [[Yocto_Project_v2.3_Status]]
| [[Yocto_Project_2.3_Release_Test_Plan | Yocto_2.3_Overall_Test_Plan]]
| [[Yocto_Project_2.3_Release_Test_Plan#Execution_History | 2.3 qa run history]]
| [https://lists.yoctoproject.org/pipermail/yocto-announce/2017-May/000112.html 2.3 release notes]
|-
|-valign="top"
| Yocto Project 2.2
| Morty
| 16.0
| Community
| [[Yocto_2.2_Features]]
| [[Yocto_2.2_Schedule]]
| [[Yocto_Project_v2.2_Status]]
| [[Yocto_2.2_Overall_Test_Plan]]
| [[Yocto_Project_2.2_Release_Test_Plan#Execution_History | 2.2 qa run history]]
| [https://lists.yoctoproject.org/pipermail/yocto-announce/2016-November/000101.html 2.2 release notes]
|-
|-valign="top"
| Yocto Project 2.1
| Krogoth
| 15.0
| Community
| [[Yocto_2.1_Features]]
| [[Yocto_2.1_Schedule]]
| [[Yocto_Project_v2.1_Status]]
| [[Yocto_2.1_Overall_Test_Plan]]
| [[2.1 qa run history]]
| [https://lists.yoctoproject.org/pipermail/yocto-announce/2016-May/000089.html 2.1 release notes]
|-
|-valign="top"
| Yocto Project 2.0
| Jethro
| 14.0
| Community
| [[Yocto_1.9_Features]]
| [[Yocto_1.9_Schedule]]
| [[Yocto_Project_v1.9_Status]]
|
| [[1.9 qa run history]]
| [https://lists.yoctoproject.org/pipermail/yocto-announce/2015-November/000076.html 2.0 release notes]
|-valign="top"
| Yocto Project 1.8
| Fido
| 13.0
| Community
| [[Yocto_1.8_Features]]
| [[Yocto_1.8_Schedule]]
| [[Yocto_Project_v1.8_Status]]
| [[Yocto_1.8_Overall_Test_Plan]]
| [[1.8 qa run history]]
| [https://lists.yoctoproject.org/pipermail/yocto-announce/2015-April/000062.html 1.8 release notes]
|-
| Yocto Project 1.7
| Dizzy
| 12.0
| Community
| [[Yocto_1.7_Features]]
| [[Yocto_1.7_Schedule]]
| [[Yocto_Project_v1.7_Status]]
| [[Yocto_1.7_Overall_Test_Plan]]
| [[1.7 qa run history]]
| [https://lists.yoctoproject.org/pipermail/yocto-announce/2014-October/000053.html 1.7 release notes]
|-
| Yocto Project 1.6
| Daisy
| 11.0
| Community
| [[Yocto_1.6_Features]]
| [[Yocto_1.6_Schedule]]
| [[Yocto_Project_v1.6_Status]]
| [[Yocto_1.6_Overall_Test_Plan]]
| [[1.6 qa run history]]
| [https://lists.yoctoproject.org/pipermail/yocto-announce/2014-April/000045.html 1.6 release notes]
|-
| Yocto Project 1.5
| Dora
| 10.0
| Community
| [[Yocto_1.5_Features]]
| [[Yocto_1.5_Schedule]]
| [[Yocto_Project_v1.5_Status]]
| [[Yocto_1.5_Overall_Test_Plan]]
| [[1.5 qa run history]]
| [https://lists.yoctoproject.org/pipermail/yocto-announce/2013-October/000037.html 1.5 release notes]
|-
| Yocto Project 1.4
| Dylan
| 9.0
| Community
| [[Yocto_1.4_Features]]
| [[Yocto_1.4_Schedule]]
| [[Yocto_Project_v1.4_Status]]
| [[Yocto_1.4_Overall_Test_Plan]]
| [[Yocto_1.4_Milestone_Test_Report]]
| [https://lists.yoctoproject.org/pipermail/yocto-announce/2013-April/000027.html 1.4 release notes]
|-
| Yocto Project 1.3
| Danny
| 8.0
| Community
| [[Yocto_1.3_Features]]
| [[Yocto_1.3_Schedule]]
| [[Yocto_Project_v1.3_Status]]
| [[Yocto_1.3_Overall_Test_Plan]]
| [[Yocto_1.3_Milestone_Test_Report]]
| [https://lists.yoctoproject.org/pipermail/yocto-announce/2012-October/000020.html 1.3 release notes]
|-
| Yocto Project 1.2
| Denzil
| 7.0
| Community
| [[Yocto_1.2_Features]]
| [[Yocto_1.2_Schedule]]
| [[Yocto_Project_v1.2_Status]]
| [[Yocto_1.2_Overall_Test_Plan]]
| [[Yocto_1.2_Milestone_Test_Report]]
| [https://lists.yoctoproject.org/pipermail/yocto-announce/2012-April/000009.html 1.2 release notes]
|-
| Yocto Project 1.1
| Edison
| 6.0
| Community
| [[Yocto_1.1_Features]]
| [[Yocto_1.1_Schedule]]
| [[Yocto_Project_v1.1_Release_Criteria]]
| [[Yocto_1.1_Overall_Test_Plan]]
| [[Yocto_1.1_Milestone_Test_Report]]
|
|-
| Yocto Project 1.0
| Bernard
| 5.0
| Community
| [[Yocto_Features]]
| [[Yocto_1.0_Schedule]]
| [[Yocto_Project_v1.0_Release_Criteria]]
| [[Yocto_1.0_Overall_Test_Plan]]
|
|
|}

Releases

2025-05-07T23:56:28Z

MichaelHalstead: /* Release Activity */ EOL not Future

== Release Activity==

See also [https://docs.yoctoproject.org/dev/_images/releases.svg a graphical release timeline].

Releases can be downloaded at https://www.yoctoproject.org/software-overview/downloads/

{| class="wikitable" border="2"
!Codename
!Yocto Project Version
!Release Date
!Current Version
!Support Level
!Poky Version
!BitBake branch
! Maintainer
!Notes
|-
|Wrynose
|6.0
| April 2026
|
|Future
|N/A
|2.16
|Richard Purdie <richard.purdie@linuxfoundation.org>
|
|-
|Whinlatter
|5.3
| October 2025
|
|Future
|N/A
|2.14
|Richard Purdie <richard.purdie@linuxfoundation.org>
|[[Recipe_Versions|Recipe versions]]
|-
|Walnascar (aka Walna)
|5.2
| April 2025
|
|Support for 7 months (until November 2025)
|N/A
|2.12
|Richard Purdie <richard.purdie@linuxfoundation.org>
|[[Recipe_Versions|Recipe versions]]
|-
|Styhead (like 'try head')
|5.1
| October 2024
|5.1.4 (April 2025)
|EOL
|N/A
|2.10
|Steve Sakoman <steve@sakoman.com>
|
|-
|Scarthgap
|5.0
| April 2024
| 5.0.9 (May 2025)
|Long Term Support (until April 2028)
|N/A
|2.8
|Steve Sakoman <steve@sakoman.com>
|[[Recipe_Versions|Recipe versions]]
|-
|-style="color: slategray;"
|Nanbield (like 'man field')
|4.3
| November 2023
| 4.3.4 (April 2024)
| EOL
|N/A
|2.6
|Steve Sakoman <steve@sakoman.com>
|- style="color: slategray;"
|Mickledore
|4.2
| May 2023
| 4.2.4 (December 2023)
| EOL
|N/A
|2.4
|Steve Sakoman <steve@sakoman.com>
|-style="color: slategray;"
|Langdale
|4.1
| October 2022
| 4.1.4 (May 2023)
| EOL
|N/A
|2.2
|Steve Sakoman <steve@sakoman.com>
|-
|Kirkstone (like 'kirk stun')
|4.0
|May 2022
|4.0.26 (April 2025)
|Long Term Support (Apr. 2026¹)
|N/A
|2.0
|Steve Sakoman <steve@sakoman.com>
|-
|-style="color: slategray;"
|Honister
|3.4
|October 2021
|3.4.4 (May 2022)
|EOL
|N/A
|1.52
|Anuj Mittal <anuj.mittal@intel.com>
|-
|-style="color: slategray;"
|Hardknott
|3.3
|April 2021
|3.3.6 (April 2022)
|EOL
|N/A
|1.50
|Anuj Mittal <anuj.mittal@intel.com>
|-
|-style="color: slategray;"
|Gatesgarth
|3.2
|Oct 2020
|3.2.4 (May 2021)
|EOL
|N/A
|1.48
|Anuj Mittal <anuj.mittal@intel.com>
|-
|-style="color: slategray;"
|Dunfell
|3.1
|April 2020
|3.1.33 (May 2024)
| EOL - LTS¹
|23.0
|1.46
|Steve Sakoman <steve@sakoman.com>
|-style="color: slategray;"
|Zeus
|3.0
|October 2019
|3.0.4 (August 2020)
|EOL
|22.0.3
|1.44
| Anuj/Armin
|-style="color: slategray;"
|Warrior
|2.7
|April 2019
|2.7.4 (June 2020)
|EOL
|21.0
|1.42
|Armin Kuster <akuster808@gmail.com>
|-style="color: slategray;"
|Thud
|2.6
|Nov 2018
|2.6.4 (October 2019)
|EOL
|20.0
|1.40
| Armin Kuster <akuster808@gmail.com>
|-style="color: slategray;"
|Sumo
|2.5
|April 2018
|2.5.3 (April 2019)
|EOL
|19.0
|1.38
| Armin Kuster <akuster808@gmail.com>
|-style="color: slategray;"
|Rocko
|2.4
|Oct 2017
|2.4.4 (November 2018)
|EOL
|18.0
|1.36
| Armin Kuster <akuster808@gmail.com>
|-style="color: slategray;"
|Pyro
|2.3
|May 2017
|2.3.4 (July 2018)
|EOL
|17.0
|1.34
| Armin Kuster <akuster808@gmail.com>
|-style="color: slategray;"
|Morty
|2.2
|Nov 2016
|2.2.4 (July 2018)
|EOL
|16.0
|1.32
| Armin Kuster <akuster808@gmail.com>
|-style="color: slategray;"
|Krogoth
|2.1
|Apr 2016
|2.1.3 (July 2017)
|EOL
|15.0
|1.30
| Armin Kuster <akuster808@gmail.com>
|-style="color: slategray;"
|Jethro
|2.0
|Nov 2015
|2.0.3 (January 2017)
|EOL
|14.0
|1.28
|Robert Yang <liezhi.yang@windriver.com>
|-style="color: slategray;"
|Fido
|1.8
|Apr 2015
|1.8.2
|EOL
|13.0
|1.26
|Joshua Lock <joshua.g.lock@intel.com>
|-style="color: slategray;"
|Dizzy
|1.7
|Oct 2014
|1.7.3
|EOL
|12.0
|1.24
| Armin Kuster <akuster808@gmail.com>
|-style="color: slategray;"
|Daisy
|1.6
|Apr 2014
|1.6.3
|EOL
|11.0
|1.22
| Saul Wold <sgw@linux.intel.com>
|-style="color: slategray;"
|Dora
|1.5
|Oct 2013
|1.5.4
|EOL
|10.0
|1.20
| Robert Yang <liezhi.yang@windriver.com>
|-style="color: slategray;"
|Dylan
|1.4
|Apr 2013
|1.4.3
|EOL
|9.0
|1.18
| Paul Eggleton <paul.eggleton@linux.intel.com>
|-style="color: slategray;"
|Danny
|1.3
|Oct 2012
|1.3.2
|EOL
|8.0
|1.16
|Ross Burton <ross.burton@intel.com>
|-style="color: slategray;"
|Denzil
|1.2
|Apr 2012
|1.2.2
|EOL
|7.0
|1.15
|-style="color: slategray;"
|Edison
|1.1
|Oct 2011
|1.1.2
|EOL
|6.0
|1.13
|-style="color: slategray;"
|Bernard
|1.0
|Apr 2011
|1.0.2
|EOL
|5.0
|1.11
|-style="color: slategray;"
|Laverne
|0.9
|Oct 2010
|
|
|4.0
|1.11
|-style="color: slategray;"
|Green
|N/A
|11 June 2010
|
|
|3.3
|
|-style="color: slategray;"
|Purple
|N/A
|15 Dec 2009
|
|
|3.2
|
|-style="color: slategray;"
|Pinky
|N/A
|12 Nov 2009
|
|
|3.1
|
|-style="color: slategray;"
|Blinky
|N/A
|1 Aug 2007
|
|
|3.0
|
|-style="color: slategray;"
|Clyde
|N/A
|19 Jan 2007
|
|
|2.0
|
|-style="color: slategray;"
|Inky
|N/A
|10 Feb 2006
|
|
|1.0
|
|}

'''Note:''' see also [[Stable Release and LTS]], [[Linux Yocto]], [[Planning]] and [[Release Feature Table]] pages. EOL means some community support on email lists but no commit updates in the repos. There is also OS Vendor support for some Yocto EOL releases.

¹ The 3.1 series and 4.0 were originally planned for two years but extended to four. Future LTS releases are planned for 4 years.

== Releases Links==
{| class="wikitable" border="2"
| align="center" style="background:#f0f0f0;"|'''Yocto Project Release'''
| align="center" style="background:#f0f0f0;"|'''Code Name'''
| align="center" style="background:#f0f0f0;"|'''Poky version'''
| align="center" style="background:#f0f0f0;"|'''Maintainer'''
| align="center" style="background:#f0f0f0;"|'''Features'''
| align="center" style="background:#f0f0f0;"|'''Schedule'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''QA Test Plan'''
| align="center" style="background:#f0f0f0;"|'''QA Test Report'''
| align="center" style="background:#f0f0f0;"|'''Release notes'''

|-valign="top"
| Yocto Project 3.4
| Honister
| 26.0
| Anuj Mittal
| [[Yocto_3.4_Features]]
| [[Yocto_3.4_Schedule]]
| [[Yocto_Project_v3.4_Status]]
| [[Yocto_Project_3.4_Release_Test_Plan | Yocto_3.4_Overall_Test_Plan]]
| [[Yocto_Project_3.4_Release_Test_Plan#Execution_History | 3.4 qa run history]]
| [https://lists.yoctoproject.org/g/yocto-announce/message/229 3.4 release notes]
|-
| Yocto Project 3.3
| Hardknott
| 25.0
| Anuj Mittal
| [[Yocto_3.3_Features]]
| [[Yocto_3.3_Schedule]]
| [[Yocto_Project_v3.3_Status]]
| [[Yocto_Project_3.3_Release_Test_Plan | Yocto_3.3_Overall_Test_Plan]]
| [[Yocto_Project_3.3_Release_Test_Plan#Execution_History | 3.3 qa run history]]
| [https://lists.yoctoproject.org/g/yocto-announce/message/215 3.3 release notes]
|-
| Yocto Project 3.2
| Gatesgarth
| 24.0
| Anuj Mittal
| [[Yocto_3.2_Features]]
| [[Yocto_3.2_Schedule]]
| [[Yocto_Project_v3.2_Status]]
| [[Yocto_Project_3.2_Release_Test_Plan | Yocto_3.2_Overall_Test_Plan]]
| [[Yocto_Project_3.2_Release_Test_Plan#Execution_History | 3.2 qa run history]]
| [https://lists.yoctoproject.org/g/yocto/message/51262 3.2 release notes]
|-
|-valign="top"
| Yocto Project 3.1
| Dunfell
| 23.0
| Steve Sakoman
| [[Yocto_3.1_Features]]
| [[Yocto_3.1_Schedule]]
| [[Yocto_Project_v3.1_Status]]
| [[Yocto_Project_3.1_Release_Test_Plan | Yocto_3.1_Overall_Test_Plan]]
| [[Yocto_Project_3.1_Release_Test_Plan#Execution_History | 3.1 qa run history]]
| [https://lists.yoctoproject.org/g/yocto/message/49201 3.1 release notes]
|-

|-valign="top"
| Yocto Project 3.0
| Zeus
| 22.0
| Armin Kuster/Anuj Mittal
| [[Yocto_2.8_Features]]
| [[Yocto_2.8_Schedule]]
| [[Yocto_Project_v2.8_Status]]
| [[Yocto_Project_2.8_Release_Test_Plan | Yocto_2.8_Overall_Test_Plan]]
| [[Yocto_Project_2.8_Release_Test_Plan#Execution_History | 2.8 qa run history]]
| [https://lists.yoctoproject.org/pipermail/yocto/2019-October/047111.html 3.0 release notes]
|-
|-valign="top"
| Yocto Project 2.7
| Warrior
| 21.0
| Community
| [[Yocto_2.7_Features]]
| [[Yocto_2.7_Schedule]]
| [[Yocto_Project_v2.7_Status]]
| [[Yocto_Project_2.7_Release_Test_Plan | Yocto_2.7_Overall_Test_Plan]]
| [[Yocto_Project_2.7_Release_Test_Plan#Execution_History | 2.7 qa run history]]
| [https://lists.yoctoproject.org/pipermail/yocto/2019-May/045028.html 2.7 release notes]
|-
|-valign="top"
| Yocto Project 2.6
| Thud
| 20.0
| Community
| [[Yocto_2.6_Features]]
| [[Yocto_2.6_Schedule]]
| [[Yocto_Project_v2.6_Status]]
| [[Yocto_Project_2.6_Release_Test_Plan | Yocto_2.6_Overall_Test_Plan]]
| [[Yocto_Project_2.6_Release_Test_Plan#Execution_History | 2.6 qa run history]]
| [https://lists.yoctoproject.org/pipermail/yocto-announce/2018-November/000147.html 2.6 release notes]
|-
|-valign="top"
| Yocto Project 2.5
| Sumo
| 19.0
| Community
| [[Yocto_2.5_Features]]
| [[Yocto_2.5_Schedule]]
| [[Yocto_Project_v2.5_Status]]
| [[Yocto_Project_2.5_Release_Test_Plan | Yocto_2.5_Overall_Test_Plan]]
| [[Yocto_Project_2.5_Release_Test_Plan#Execution_History | 2.5 qa run history]]
| [https://lists.yoctoproject.org/pipermail/yocto-announce/2018-May/000136.html 2.5 release notes]
|-
|-valign="top"
| Yocto Project 2.4
| Rocko
| 18.0
| Community
| [[Yocto_2.4_Features]]
| [[Yocto_2.4_Schedule]]
| [[Yocto_Project_v2.4_Status]]
| [[Yocto_Project_2.4_Release_Test_Plan | Yocto_2.4_Overall_Test_Plan]]
| [[Yocto_Project_2.4_Release_Test_Plan#Execution_History | 2.4 qa run history]]
| [https://lists.yoctoproject.org/pipermail/yocto-announce/2017-October/000125.html 2.4 release notes]
|-
|-valign="top"
| Yocto Project 2.3
| Pyro
| 17.0
| Community
| [[Yocto_2.3_Features]]
| [[Yocto_2.3_Schedule]]
| [[Yocto_Project_v2.3_Status]]
| [[Yocto_Project_2.3_Release_Test_Plan | Yocto_2.3_Overall_Test_Plan]]
| [[Yocto_Project_2.3_Release_Test_Plan#Execution_History | 2.3 qa run history]]
| [https://lists.yoctoproject.org/pipermail/yocto-announce/2017-May/000112.html 2.3 release notes]
|-
|-valign="top"
| Yocto Project 2.2
| Morty
| 16.0
| Community
| [[Yocto_2.2_Features]]
| [[Yocto_2.2_Schedule]]
| [[Yocto_Project_v2.2_Status]]
| [[Yocto_2.2_Overall_Test_Plan]]
| [[Yocto_Project_2.2_Release_Test_Plan#Execution_History | 2.2 qa run history]]
| [https://lists.yoctoproject.org/pipermail/yocto-announce/2016-November/000101.html 2.2 release notes]
|-
|-valign="top"
| Yocto Project 2.1
| Krogoth
| 15.0
| Community
| [[Yocto_2.1_Features]]
| [[Yocto_2.1_Schedule]]
| [[Yocto_Project_v2.1_Status]]
| [[Yocto_2.1_Overall_Test_Plan]]
| [[2.1 qa run history]]
| [https://lists.yoctoproject.org/pipermail/yocto-announce/2016-May/000089.html 2.1 release notes]
|-
|-valign="top"
| Yocto Project 2.0
| Jethro
| 14.0
| Community
| [[Yocto_1.9_Features]]
| [[Yocto_1.9_Schedule]]
| [[Yocto_Project_v1.9_Status]]
|
| [[1.9 qa run history]]
| [https://lists.yoctoproject.org/pipermail/yocto-announce/2015-November/000076.html 2.0 release notes]
|-valign="top"
| Yocto Project 1.8
| Fido
| 13.0
| Community
| [[Yocto_1.8_Features]]
| [[Yocto_1.8_Schedule]]
| [[Yocto_Project_v1.8_Status]]
| [[Yocto_1.8_Overall_Test_Plan]]
| [[1.8 qa run history]]
| [https://lists.yoctoproject.org/pipermail/yocto-announce/2015-April/000062.html 1.8 release notes]
|-
| Yocto Project 1.7
| Dizzy
| 12.0
| Community
| [[Yocto_1.7_Features]]
| [[Yocto_1.7_Schedule]]
| [[Yocto_Project_v1.7_Status]]
| [[Yocto_1.7_Overall_Test_Plan]]
| [[1.7 qa run history]]
| [https://lists.yoctoproject.org/pipermail/yocto-announce/2014-October/000053.html 1.7 release notes]
|-
| Yocto Project 1.6
| Daisy
| 11.0
| Community
| [[Yocto_1.6_Features]]
| [[Yocto_1.6_Schedule]]
| [[Yocto_Project_v1.6_Status]]
| [[Yocto_1.6_Overall_Test_Plan]]
| [[1.6 qa run history]]
| [https://lists.yoctoproject.org/pipermail/yocto-announce/2014-April/000045.html 1.6 release notes]
|-
| Yocto Project 1.5
| Dora
| 10.0
| Community
| [[Yocto_1.5_Features]]
| [[Yocto_1.5_Schedule]]
| [[Yocto_Project_v1.5_Status]]
| [[Yocto_1.5_Overall_Test_Plan]]
| [[1.5 qa run history]]
| [https://lists.yoctoproject.org/pipermail/yocto-announce/2013-October/000037.html 1.5 release notes]
|-
| Yocto Project 1.4
| Dylan
| 9.0
| Community
| [[Yocto_1.4_Features]]
| [[Yocto_1.4_Schedule]]
| [[Yocto_Project_v1.4_Status]]
| [[Yocto_1.4_Overall_Test_Plan]]
| [[Yocto_1.4_Milestone_Test_Report]]
| [https://lists.yoctoproject.org/pipermail/yocto-announce/2013-April/000027.html 1.4 release notes]
|-
| Yocto Project 1.3
| Danny
| 8.0
| Community
| [[Yocto_1.3_Features]]
| [[Yocto_1.3_Schedule]]
| [[Yocto_Project_v1.3_Status]]
| [[Yocto_1.3_Overall_Test_Plan]]
| [[Yocto_1.3_Milestone_Test_Report]]
| [https://lists.yoctoproject.org/pipermail/yocto-announce/2012-October/000020.html 1.3 release notes]
|-
| Yocto Project 1.2
| Denzil
| 7.0
| Community
| [[Yocto_1.2_Features]]
| [[Yocto_1.2_Schedule]]
| [[Yocto_Project_v1.2_Status]]
| [[Yocto_1.2_Overall_Test_Plan]]
| [[Yocto_1.2_Milestone_Test_Report]]
| [https://lists.yoctoproject.org/pipermail/yocto-announce/2012-April/000009.html 1.2 release notes]
|-
| Yocto Project 1.1
| Edison
| 6.0
| Community
| [[Yocto_1.1_Features]]
| [[Yocto_1.1_Schedule]]
| [[Yocto_Project_v1.1_Release_Criteria]]
| [[Yocto_1.1_Overall_Test_Plan]]
| [[Yocto_1.1_Milestone_Test_Report]]
|
|-
| Yocto Project 1.0
| Bernard
| 5.0
| Community
| [[Yocto_Features]]
| [[Yocto_1.0_Schedule]]
| [[Yocto_Project_v1.0_Release_Criteria]]
| [[Yocto_1.0_Overall_Test_Plan]]
|
|
|}

Releases

2025-05-07T23:55:09Z

MichaelHalstead: /* Release Activity */ walna is out

== Release Activity==

See also [https://docs.yoctoproject.org/dev/_images/releases.svg a graphical release timeline].

Releases can be downloaded at https://www.yoctoproject.org/software-overview/downloads/

{| class="wikitable" border="2"
!Codename
!Yocto Project Version
!Release Date
!Current Version
!Support Level
!Poky Version
!BitBake branch
! Maintainer
!Notes
|-
|Wrynose
|6.0
| April 2026
|
|Future
|N/A
|2.16
|Richard Purdie <richard.purdie@linuxfoundation.org>
|
|-
|Whinlatter
|5.3
| October 2025
|
|Future
|N/A
|2.14
|Richard Purdie <richard.purdie@linuxfoundation.org>
|[[Recipe_Versions|Recipe versions]]
|-
|Walnascar (aka Walna)
|5.2
| April 2025
|
|Support for 7 months (until November 2025)
|N/A
|2.12
|Richard Purdie <richard.purdie@linuxfoundation.org>
|[[Recipe_Versions|Recipe versions]]
|-
|Styhead (like 'try head')
|5.1
| October 2024
|5.1.4 (April 2025)
|Future
|N/A
|2.10
|Steve Sakoman <steve@sakoman.com>
|
|-
|Scarthgap
|5.0
| April 2024
| 5.0.9 (May 2025)
|Long Term Support (until April 2028)
|N/A
|2.8
|Steve Sakoman <steve@sakoman.com>
|[[Recipe_Versions|Recipe versions]]
|-
|-style="color: slategray;"
|Nanbield (like 'man field')
|4.3
| November 2023
| 4.3.4 (April 2024)
| EOL
|N/A
|2.6
|Steve Sakoman <steve@sakoman.com>
|- style="color: slategray;"
|Mickledore
|4.2
| May 2023
| 4.2.4 (December 2023)
| EOL
|N/A
|2.4
|Steve Sakoman <steve@sakoman.com>
|-style="color: slategray;"
|Langdale
|4.1
| October 2022
| 4.1.4 (May 2023)
| EOL
|N/A
|2.2
|Steve Sakoman <steve@sakoman.com>
|-
|Kirkstone (like 'kirk stun')
|4.0
|May 2022
|4.0.26 (April 2025)
|Long Term Support (Apr. 2026¹)
|N/A
|2.0
|Steve Sakoman <steve@sakoman.com>
|-
|-style="color: slategray;"
|Honister
|3.4
|October 2021
|3.4.4 (May 2022)
|EOL
|N/A
|1.52
|Anuj Mittal <anuj.mittal@intel.com>
|-
|-style="color: slategray;"
|Hardknott
|3.3
|April 2021
|3.3.6 (April 2022)
|EOL
|N/A
|1.50
|Anuj Mittal <anuj.mittal@intel.com>
|-
|-style="color: slategray;"
|Gatesgarth
|3.2
|Oct 2020
|3.2.4 (May 2021)
|EOL
|N/A
|1.48
|Anuj Mittal <anuj.mittal@intel.com>
|-
|-style="color: slategray;"
|Dunfell
|3.1
|April 2020
|3.1.33 (May 2024)
| EOL - LTS¹
|23.0
|1.46
|Steve Sakoman <steve@sakoman.com>
|-style="color: slategray;"
|Zeus
|3.0
|October 2019
|3.0.4 (August 2020)
|EOL
|22.0.3
|1.44
| Anuj/Armin
|-style="color: slategray;"
|Warrior
|2.7
|April 2019
|2.7.4 (June 2020)
|EOL
|21.0
|1.42
|Armin Kuster <akuster808@gmail.com>
|-style="color: slategray;"
|Thud
|2.6
|Nov 2018
|2.6.4 (October 2019)
|EOL
|20.0
|1.40
| Armin Kuster <akuster808@gmail.com>
|-style="color: slategray;"
|Sumo
|2.5
|April 2018
|2.5.3 (April 2019)
|EOL
|19.0
|1.38
| Armin Kuster <akuster808@gmail.com>
|-style="color: slategray;"
|Rocko
|2.4
|Oct 2017
|2.4.4 (November 2018)
|EOL
|18.0
|1.36
| Armin Kuster <akuster808@gmail.com>
|-style="color: slategray;"
|Pyro
|2.3
|May 2017
|2.3.4 (July 2018)
|EOL
|17.0
|1.34
| Armin Kuster <akuster808@gmail.com>
|-style="color: slategray;"
|Morty
|2.2
|Nov 2016
|2.2.4 (July 2018)
|EOL
|16.0
|1.32
| Armin Kuster <akuster808@gmail.com>
|-style="color: slategray;"
|Krogoth
|2.1
|Apr 2016
|2.1.3 (July 2017)
|EOL
|15.0
|1.30
| Armin Kuster <akuster808@gmail.com>
|-style="color: slategray;"
|Jethro
|2.0
|Nov 2015
|2.0.3 (January 2017)
|EOL
|14.0
|1.28
|Robert Yang <liezhi.yang@windriver.com>
|-style="color: slategray;"
|Fido
|1.8
|Apr 2015
|1.8.2
|EOL
|13.0
|1.26
|Joshua Lock <joshua.g.lock@intel.com>
|-style="color: slategray;"
|Dizzy
|1.7
|Oct 2014
|1.7.3
|EOL
|12.0
|1.24
| Armin Kuster <akuster808@gmail.com>
|-style="color: slategray;"
|Daisy
|1.6
|Apr 2014
|1.6.3
|EOL
|11.0
|1.22
| Saul Wold <sgw@linux.intel.com>
|-style="color: slategray;"
|Dora
|1.5
|Oct 2013
|1.5.4
|EOL
|10.0
|1.20
| Robert Yang <liezhi.yang@windriver.com>
|-style="color: slategray;"
|Dylan
|1.4
|Apr 2013
|1.4.3
|EOL
|9.0
|1.18
| Paul Eggleton <paul.eggleton@linux.intel.com>
|-style="color: slategray;"
|Danny
|1.3
|Oct 2012
|1.3.2
|EOL
|8.0
|1.16
|Ross Burton <ross.burton@intel.com>
|-style="color: slategray;"
|Denzil
|1.2
|Apr 2012
|1.2.2
|EOL
|7.0
|1.15
|-style="color: slategray;"
|Edison
|1.1
|Oct 2011
|1.1.2
|EOL
|6.0
|1.13
|-style="color: slategray;"
|Bernard
|1.0
|Apr 2011
|1.0.2
|EOL
|5.0
|1.11
|-style="color: slategray;"
|Laverne
|0.9
|Oct 2010
|
|
|4.0
|1.11
|-style="color: slategray;"
|Green
|N/A
|11 June 2010
|
|
|3.3
|
|-style="color: slategray;"
|Purple
|N/A
|15 Dec 2009
|
|
|3.2
|
|-style="color: slategray;"
|Pinky
|N/A
|12 Nov 2009
|
|
|3.1
|
|-style="color: slategray;"
|Blinky
|N/A
|1 Aug 2007
|
|
|3.0
|
|-style="color: slategray;"
|Clyde
|N/A
|19 Jan 2007
|
|
|2.0
|
|-style="color: slategray;"
|Inky
|N/A
|10 Feb 2006
|
|
|1.0
|
|}

'''Note:''' see also [[Stable Release and LTS]], [[Linux Yocto]], [[Planning]] and [[Release Feature Table]] pages. EOL means some community support on email lists but no commit updates in the repos. There is also OS Vendor support for some Yocto EOL releases.

¹ The 3.1 series and 4.0 were originally planned for two years but extended to four. Future LTS releases are planned for 4 years.

== Releases Links==
{| class="wikitable" border="2"
| align="center" style="background:#f0f0f0;"|'''Yocto Project Release'''
| align="center" style="background:#f0f0f0;"|'''Code Name'''
| align="center" style="background:#f0f0f0;"|'''Poky version'''
| align="center" style="background:#f0f0f0;"|'''Maintainer'''
| align="center" style="background:#f0f0f0;"|'''Features'''
| align="center" style="background:#f0f0f0;"|'''Schedule'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''QA Test Plan'''
| align="center" style="background:#f0f0f0;"|'''QA Test Report'''
| align="center" style="background:#f0f0f0;"|'''Release notes'''

|-valign="top"
| Yocto Project 3.4
| Honister
| 26.0
| Anuj Mittal
| [[Yocto_3.4_Features]]
| [[Yocto_3.4_Schedule]]
| [[Yocto_Project_v3.4_Status]]
| [[Yocto_Project_3.4_Release_Test_Plan | Yocto_3.4_Overall_Test_Plan]]
| [[Yocto_Project_3.4_Release_Test_Plan#Execution_History | 3.4 qa run history]]
| [https://lists.yoctoproject.org/g/yocto-announce/message/229 3.4 release notes]
|-
| Yocto Project 3.3
| Hardknott
| 25.0
| Anuj Mittal
| [[Yocto_3.3_Features]]
| [[Yocto_3.3_Schedule]]
| [[Yocto_Project_v3.3_Status]]
| [[Yocto_Project_3.3_Release_Test_Plan | Yocto_3.3_Overall_Test_Plan]]
| [[Yocto_Project_3.3_Release_Test_Plan#Execution_History | 3.3 qa run history]]
| [https://lists.yoctoproject.org/g/yocto-announce/message/215 3.3 release notes]
|-
| Yocto Project 3.2
| Gatesgarth
| 24.0
| Anuj Mittal
| [[Yocto_3.2_Features]]
| [[Yocto_3.2_Schedule]]
| [[Yocto_Project_v3.2_Status]]
| [[Yocto_Project_3.2_Release_Test_Plan | Yocto_3.2_Overall_Test_Plan]]
| [[Yocto_Project_3.2_Release_Test_Plan#Execution_History | 3.2 qa run history]]
| [https://lists.yoctoproject.org/g/yocto/message/51262 3.2 release notes]
|-
|-valign="top"
| Yocto Project 3.1
| Dunfell
| 23.0
| Steve Sakoman
| [[Yocto_3.1_Features]]
| [[Yocto_3.1_Schedule]]
| [[Yocto_Project_v3.1_Status]]
| [[Yocto_Project_3.1_Release_Test_Plan | Yocto_3.1_Overall_Test_Plan]]
| [[Yocto_Project_3.1_Release_Test_Plan#Execution_History | 3.1 qa run history]]
| [https://lists.yoctoproject.org/g/yocto/message/49201 3.1 release notes]
|-

|-valign="top"
| Yocto Project 3.0
| Zeus
| 22.0
| Armin Kuster/Anuj Mittal
| [[Yocto_2.8_Features]]
| [[Yocto_2.8_Schedule]]
| [[Yocto_Project_v2.8_Status]]
| [[Yocto_Project_2.8_Release_Test_Plan | Yocto_2.8_Overall_Test_Plan]]
| [[Yocto_Project_2.8_Release_Test_Plan#Execution_History | 2.8 qa run history]]
| [https://lists.yoctoproject.org/pipermail/yocto/2019-October/047111.html 3.0 release notes]
|-
|-valign="top"
| Yocto Project 2.7
| Warrior
| 21.0
| Community
| [[Yocto_2.7_Features]]
| [[Yocto_2.7_Schedule]]
| [[Yocto_Project_v2.7_Status]]
| [[Yocto_Project_2.7_Release_Test_Plan | Yocto_2.7_Overall_Test_Plan]]
| [[Yocto_Project_2.7_Release_Test_Plan#Execution_History | 2.7 qa run history]]
| [https://lists.yoctoproject.org/pipermail/yocto/2019-May/045028.html 2.7 release notes]
|-
|-valign="top"
| Yocto Project 2.6
| Thud
| 20.0
| Community
| [[Yocto_2.6_Features]]
| [[Yocto_2.6_Schedule]]
| [[Yocto_Project_v2.6_Status]]
| [[Yocto_Project_2.6_Release_Test_Plan | Yocto_2.6_Overall_Test_Plan]]
| [[Yocto_Project_2.6_Release_Test_Plan#Execution_History | 2.6 qa run history]]
| [https://lists.yoctoproject.org/pipermail/yocto-announce/2018-November/000147.html 2.6 release notes]
|-
|-valign="top"
| Yocto Project 2.5
| Sumo
| 19.0
| Community
| [[Yocto_2.5_Features]]
| [[Yocto_2.5_Schedule]]
| [[Yocto_Project_v2.5_Status]]
| [[Yocto_Project_2.5_Release_Test_Plan | Yocto_2.5_Overall_Test_Plan]]
| [[Yocto_Project_2.5_Release_Test_Plan#Execution_History | 2.5 qa run history]]
| [https://lists.yoctoproject.org/pipermail/yocto-announce/2018-May/000136.html 2.5 release notes]
|-
|-valign="top"
| Yocto Project 2.4
| Rocko
| 18.0
| Community
| [[Yocto_2.4_Features]]
| [[Yocto_2.4_Schedule]]
| [[Yocto_Project_v2.4_Status]]
| [[Yocto_Project_2.4_Release_Test_Plan | Yocto_2.4_Overall_Test_Plan]]
| [[Yocto_Project_2.4_Release_Test_Plan#Execution_History | 2.4 qa run history]]
| [https://lists.yoctoproject.org/pipermail/yocto-announce/2017-October/000125.html 2.4 release notes]
|-
|-valign="top"
| Yocto Project 2.3
| Pyro
| 17.0
| Community
| [[Yocto_2.3_Features]]
| [[Yocto_2.3_Schedule]]
| [[Yocto_Project_v2.3_Status]]
| [[Yocto_Project_2.3_Release_Test_Plan | Yocto_2.3_Overall_Test_Plan]]
| [[Yocto_Project_2.3_Release_Test_Plan#Execution_History | 2.3 qa run history]]
| [https://lists.yoctoproject.org/pipermail/yocto-announce/2017-May/000112.html 2.3 release notes]
|-
|-valign="top"
| Yocto Project 2.2
| Morty
| 16.0
| Community
| [[Yocto_2.2_Features]]
| [[Yocto_2.2_Schedule]]
| [[Yocto_Project_v2.2_Status]]
| [[Yocto_2.2_Overall_Test_Plan]]
| [[Yocto_Project_2.2_Release_Test_Plan#Execution_History | 2.2 qa run history]]
| [https://lists.yoctoproject.org/pipermail/yocto-announce/2016-November/000101.html 2.2 release notes]
|-
|-valign="top"
| Yocto Project 2.1
| Krogoth
| 15.0
| Community
| [[Yocto_2.1_Features]]
| [[Yocto_2.1_Schedule]]
| [[Yocto_Project_v2.1_Status]]
| [[Yocto_2.1_Overall_Test_Plan]]
| [[2.1 qa run history]]
| [https://lists.yoctoproject.org/pipermail/yocto-announce/2016-May/000089.html 2.1 release notes]
|-
|-valign="top"
| Yocto Project 2.0
| Jethro
| 14.0
| Community
| [[Yocto_1.9_Features]]
| [[Yocto_1.9_Schedule]]
| [[Yocto_Project_v1.9_Status]]
|
| [[1.9 qa run history]]
| [https://lists.yoctoproject.org/pipermail/yocto-announce/2015-November/000076.html 2.0 release notes]
|-valign="top"
| Yocto Project 1.8
| Fido
| 13.0
| Community
| [[Yocto_1.8_Features]]
| [[Yocto_1.8_Schedule]]
| [[Yocto_Project_v1.8_Status]]
| [[Yocto_1.8_Overall_Test_Plan]]
| [[1.8 qa run history]]
| [https://lists.yoctoproject.org/pipermail/yocto-announce/2015-April/000062.html 1.8 release notes]
|-
| Yocto Project 1.7
| Dizzy
| 12.0
| Community
| [[Yocto_1.7_Features]]
| [[Yocto_1.7_Schedule]]
| [[Yocto_Project_v1.7_Status]]
| [[Yocto_1.7_Overall_Test_Plan]]
| [[1.7 qa run history]]
| [https://lists.yoctoproject.org/pipermail/yocto-announce/2014-October/000053.html 1.7 release notes]
|-
| Yocto Project 1.6
| Daisy
| 11.0
| Community
| [[Yocto_1.6_Features]]
| [[Yocto_1.6_Schedule]]
| [[Yocto_Project_v1.6_Status]]
| [[Yocto_1.6_Overall_Test_Plan]]
| [[1.6 qa run history]]
| [https://lists.yoctoproject.org/pipermail/yocto-announce/2014-April/000045.html 1.6 release notes]
|-
| Yocto Project 1.5
| Dora
| 10.0
| Community
| [[Yocto_1.5_Features]]
| [[Yocto_1.5_Schedule]]
| [[Yocto_Project_v1.5_Status]]
| [[Yocto_1.5_Overall_Test_Plan]]
| [[1.5 qa run history]]
| [https://lists.yoctoproject.org/pipermail/yocto-announce/2013-October/000037.html 1.5 release notes]
|-
| Yocto Project 1.4
| Dylan
| 9.0
| Community
| [[Yocto_1.4_Features]]
| [[Yocto_1.4_Schedule]]
| [[Yocto_Project_v1.4_Status]]
| [[Yocto_1.4_Overall_Test_Plan]]
| [[Yocto_1.4_Milestone_Test_Report]]
| [https://lists.yoctoproject.org/pipermail/yocto-announce/2013-April/000027.html 1.4 release notes]
|-
| Yocto Project 1.3
| Danny
| 8.0
| Community
| [[Yocto_1.3_Features]]
| [[Yocto_1.3_Schedule]]
| [[Yocto_Project_v1.3_Status]]
| [[Yocto_1.3_Overall_Test_Plan]]
| [[Yocto_1.3_Milestone_Test_Report]]
| [https://lists.yoctoproject.org/pipermail/yocto-announce/2012-October/000020.html 1.3 release notes]
|-
| Yocto Project 1.2
| Denzil
| 7.0
| Community
| [[Yocto_1.2_Features]]
| [[Yocto_1.2_Schedule]]
| [[Yocto_Project_v1.2_Status]]
| [[Yocto_1.2_Overall_Test_Plan]]
| [[Yocto_1.2_Milestone_Test_Report]]
| [https://lists.yoctoproject.org/pipermail/yocto-announce/2012-April/000009.html 1.2 release notes]
|-
| Yocto Project 1.1
| Edison
| 6.0
| Community
| [[Yocto_1.1_Features]]
| [[Yocto_1.1_Schedule]]
| [[Yocto_Project_v1.1_Release_Criteria]]
| [[Yocto_1.1_Overall_Test_Plan]]
| [[Yocto_1.1_Milestone_Test_Report]]
|
|-
| Yocto Project 1.0
| Bernard
| 5.0
| Community
| [[Yocto_Features]]
| [[Yocto_1.0_Schedule]]
| [[Yocto_Project_v1.0_Release_Criteria]]
| [[Yocto_1.0_Overall_Test_Plan]]
|
|
|}

User talk:Chuckwolber

2025-03-07T18:04:34Z

MichaelHalstead: Welcome!

User:Chuckwolber

2025-03-07T18:04:34Z

MichaelHalstead: Creating user page for new user.

Software engineer. Yocto project user since 2017.

Patch Review Call

2025-02-25T22:43:40Z

MichaelHalstead:

We have patch review calls to discuss patches that are under review. Any review comments in the call should be submitted to the mailing list: the list is still the primary location for feedback.

There are two meeting times:
* Monday, 17:00 - 18:00 UK time
* Thursday, 10:00 - 11:00 UK time
The calls are held on [https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1 Zoom].

Call Details 
Meeting ID: 977 6239 7148 
Passcode: 450428 
International numbers available: https://zoom.us/u/abKnJRHtHt

The intention is to ensure that all patches merged have definitely had multiple eyes looking at them, patches that need serious review get assigned to someone, and patches that need further work get replied to on the list.

Future plans:
* Formalise the process further (prior art: the glibc patch review call)
* Move review pipeline from oe-core/master-next to patchwork
* Tooling: submit autobuilder status to patchwork so b4 can show status

Patch Review Call

2025-02-25T22:41:19Z

MichaelHalstead: Add dial-in details

We have patch review calls to discuss patches that are under review. Any review comments in the call should be submitted to the mailing list: the list is still the primary location for feedback.

There are two meeting times:
* Monday, 17:00 - 18:00 UK time
* Thursday, 10:00 - 11:00 UK time
The calls are held on [https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1 Zoom].

Call Details
Meeting ID: 977 6239 7148
Passcode: 450428

International numbers available: https://zoom.us/u/abKnJRHtHt

The intention is to ensure that all patches merged have definitely had multiple eyes looking at them, patches that need serious review get assigned to someone, and patches that need further work get replied to on the list.

Future plans:
* Formalise the process further (prior art: the glibc patch review call)
* Move review pipeline from oe-core/master-next to patchwork
* Tooling: submit autobuilder status to patchwork so b4 can show status

Patch Review Call

2025-02-25T22:39:39Z

MichaelHalstead: Add meeting link

We have patch review calls to discuss patches that are under review. Any review comments in the call should be submitted to the mailing list: the list is still the primary location for feedback.

There are two meeting times:
* Monday, 17:00 - 18:00 UK time
* Thursday, 10:00 - 11:00 UK time
The calls are held on [https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1 Zoom].

The intention is to ensure that all patches merged have definitely had multiple eyes looking at them, patches that need serious review get assigned to someone, and patches that need further work get replied to on the list.

Future plans:
* Formalise the process further (prior art: the glibc patch review call)
* Move review pipeline from oe-core/master-next to patchwork
* Tooling: submit autobuilder status to patchwork so b4 can show status

TipsAndTricks/ResolvingLocaleIssues

2024-12-03T13:45:50Z

MichaelHalstead: /* Ubuntu/Debian */

= What to do when bitbake says " Sad Locale, Need UTF-8" =
If bitbake says:
<code>
Please use a locale setting which supports utf-8.
Python can't change the filesystem locale after loading so we need a utf-8 when python starts or things won't work.
</code>
You need a locale. My example will target en_US.UTF-8. You can choose your favorite (native?) locale as long as it's UTF8.

== Ubuntu/Debian ==

<code>
tt@7e801839f06a:~/build$ sudo apt-get install locales
tt@7e801839f06a:~/build$ sudo dpkg-reconfigure locales
<pick your favorite, in my case en_US.UTF-8 UTF-8, then default the language to en_US.UTF-8>
tt@7e801839f06a:~/build$ sudo locale-gen en_US.UTF-8
Generating locales (this might take a while)...
en_US.UTF-8... done
Generation complete.
tt@7e801839f06a:~/build$ sudo update-locale LC_ALL=en_US.UTF-8 LANG=en_US.UTF-8
tt@7e801839f06a:~/build$ export LANG=en_US.UTF-8
</code>

Alternately

sudo apt-get install locales
sudo locale-gen en_US.UTF-8
sudo localectl set-locale LANG=en_US.UTF-8

== Fedora ==
=== Fedora:24 ===
<code>
sudo dnf install glibc-langpack-en
sudo dnf reinstall glibc-common
export LANG=en_US.UTF-8
</code>

== OpenSuse ==
=== OpenSuse:42.1 ===
<code>
bash-4.2$ sudo zypper install glibc-locale
bash-4.2$ export LANG=en_US.UTF-8
</code>

TipsAndTricks/ResolvingLocaleIssues

2024-12-03T13:44:20Z

MichaelHalstead: /* Ubuntu/Debian */

= What to do when bitbake says " Sad Locale, Need UTF-8" =
If bitbake says:
<code>
Please use a locale setting which supports utf-8.
Python can't change the filesystem locale after loading so we need a utf-8 when python starts or things won't work.
</code>
You need a locale. My example will target en_US.UTF-8. You can choose your favorite (native?) locale as long as it's UTF8.

== Ubuntu/Debian ==

<code>
tt@7e801839f06a:~/build$ sudo apt-get install locales
tt@7e801839f06a:~/build$ sudo dpkg-reconfigure locales
<pick your favorite, in my case en_US.UTF-8 UTF-8, then default the language to en_US.UTF-8>
tt@7e801839f06a:~/build$ sudo locale-gen en_US.UTF-8
Generating locales (this might take a while)...
en_US.UTF-8... done
Generation complete.
tt@7e801839f06a:~/build$ sudo update-locale LC_ALL=en_US.UTF-8 LANG=en_US.UTF-8
tt@7e801839f06a:~/build$ export LANG=en_US.UTF-8
</code>

Alternately
sudo localectl set-locale LANG=en_US.UTF-8

== Fedora ==
=== Fedora:24 ===
<code>
sudo dnf install glibc-langpack-en
sudo dnf reinstall glibc-common
export LANG=en_US.UTF-8
</code>

== OpenSuse ==
=== OpenSuse:42.1 ===
<code>
bash-4.2$ sudo zypper install glibc-locale
bash-4.2$ export LANG=en_US.UTF-8
</code>

User talk:Chaojun

2024-11-26T16:39:14Z

MichaelHalstead: Welcome!

User:Chaojun

2024-11-26T16:39:14Z

MichaelHalstead: Creating user page for new user.

I am an experienced software development engineer specializing in embedded systems and Linux OS customization. Currently, I am working on a project using the Yocto Project to build and optimize a customized Linux operating system tailored to meet specific hardware and functional requirements. In my work, I frequently engage in Yocto-related tasks, including writing custom recipes, building ISO images, and working with different kernel configurations.

I have extensive experience with the Yocto Project, including proficiency with the Yocto build system and related toolchains, particularly for the aarch64 architecture and systemd-boot boot manager. I am enthusiastic about contributing to and collaborating with the open-source community, and I look forward to engaging with other developers on the official Yocto platform to exchange knowledge and contribute to the project’s growth.

User talk:Jpsainfeld

2024-11-26T16:31:47Z

MichaelHalstead: Welcome!

User:Jpsainfeld

2024-11-26T16:31:47Z

MichaelHalstead: Creating user page for new user.

Embedded Platform Software Engineer with over 25 years of software development experience in various technical and cultural environments. Demonstrated ability to bring projects from inception to production to completion within budget and schedule. Intimately familiar with all processes of software development and life cycles with emphasis on projects close to hardware specifications, driver designs for OS integration or pre and post Silicon validation and test automation. Notably interested in any project where device drivers design and testing are a major component and can make valuable contributions to embedded platform projects especially in the areas of Board Support Packages for U-Boot, Linux, FreeBSD or Open-Source.

User talk:D8uv

2024-11-26T16:24:50Z

MichaelHalstead: Welcome!

User:D8uv

2024-11-26T16:24:50Z

MichaelHalstead: Creating user page for new user.

Front end web developer, currently in Urbana IL

YoctoProject Summit yps2024.12

2024-11-26T06:51:23Z

MichaelHalstead: /* Hands-on Servers Information (Pre-event Preparation) */

= The Yocto Project Summit 2024.12 =
The Yocto Project Summit, yps2024.12, is a virtual conference from December 3rd to 5th, 2024 to gather members of the Yocto Project community together to discuss ideas and present information related to The Yocto Project.

== Organizing Committee ==
The organizing committee consists of (alphabetical by first name):
* David Reyna
* Josef Holzmayr-Khosh Amoz (YP Community Manager)
* Megan Knight (Advocacy Manager)
* Philip Balister

== Registration ==

Registration Link: https://cvent.me/V5kARQ

== Platforms ==
In terms of platforms we're using:
* pretalx for the CfP and schedule
* the LF's cvent for registration
* Zoom for the conference video
* irc for the conference chat (channel #yocto-summit-2024.12 on Libera.Chat)
* Digital Ocean for the hands-on classes

== Hands-on Servers Information (Pre-event Preparation) ==
# If you already have a Digital Ocean account, skip the next 2 steps.
# To create a Digital Ocean account, please sign up @ [https://do.co/yoctoproject DigitalOcean] to receive a $200 credit for new users.
# Confirm your email and add a payment method to satisfy abuse requirements - you won't be charged unless you leave the training machine running long past the summit
# Visit https://cloud.digitalocean.com/account/api/tokens and generate a new token named '''YPSummit''', and copy the string that pops up.
# Please complete this [https://forms.gle/rPtZ84gbSmKJo2cN9 form] so your API key can be added to the provisioning scripts. It's unlikely we will be able to offer additional credit to existing account holders this year. Leave the API key blank if you'd like Yocto Project to cover training VM expenses.

After the form has been filled by all participants we will provision machines. When the machines are ready logins will be "ssh ilab01@AXAXAXAX-summit.yocto.io" where AXAXAXAX are the first 8 characters of your confirmation string. The password is the full 11 character confirmation string.

Once you have a verified working server you may delete your api key at https://cloud.digitalocean.com/account/api/tokens. Otherwise all resources will be removed after the training. Any retained servers will be billed to you after the promotional credit expires in 60 days.


Lab files will be available for download once the event begins.

== For more information ==
* https://www.yoctoproject.org/event/2024-12/
* https://pretalx.com/yocto-project-summit-2024-12/

== Slide template for presenters ==
* https://docs.google.com/presentation/d/1ttXgB8Z1gasL7ItCYZ-uXT_FmfnIgPoMK_JtjvBrj1g
** keep the first and last slides
** edit the first slide to include your name, presentation title, and (optionally) your company
** the rest of the slides are examples and can be duplicated, edited, and/or removed
** please upload your finished slides to your specific event in pretalx
** Pretalx has an upload limit of 10Mb. Please for example compress your PDF files when you "Save-as", or use a free service like "https://www.adobe.com/acrobat/online/compress-pdf.html"

Accessing Autobuilders

2024-11-11T20:37:25Z

MichaelHalstead: Update to remove typhoon directions.

==Connecting to Autobuilders==
We use an ssh jumphost called access.yoctoproject.org/access.yocto.io to connect to the autobuilders. Jumphosts enhance security by removing the threat of hijacked ssh-agents and limiting the services running on Internet exposed hosts.

===Generate keys===
In order to access any of the autobuilders your ssh public keys must first be installed. The preferred key type is ECC. RSA with 4096 bits is also acceptable. Please put your e-mail, the date of generation, and the host the key lives on in the comment. Please set a passphrase even if it's a simple one! Ideally your private key will never leave the host it is generated on - so if you have multiple machines please generate multiple keys. E-mail your '''public''' key named ~/.ssh/id_ed25519.pub or id_rsa.pub to helpdesk@yoctoproject.org. Keep id_ed25519 or id_rsa(the private key) super safe. Please never share it with anyone or copy it onto the Internet. Don't e-mail it to yourself either.

ssh-keygen -t ed25519 -C "your_email@example.com_2012-05-30_localhostname"

Substitute your own e-mail and your computer's hostname in the command above. Setting these helps with troubleshooting in the future.

===Configure ssh===
Edit ~/.ssh/config on your local machine and add:

Host access-vk.yoctoproject.org
# Make sure your username matches your account on the autobuilder
#User [username]
# Give the full path to the proper public key if needed
#IdentityFile /home/[username]/.ssh/id_rsa
# If your network requires you to use a SOCKS proxy enable it here
# ProxyCommand nc -X5 -x [proxyserver.address.company.com:1080] %h %p
# If your system uses 'ncat', rather than 'netcat', use these options to enable a SOCKS proxy
# ProxyCommand nc --proxy-type socks5 --proxy [proxyserver.address.company.com:1080] %h %p

# Valkyrie proxy through a bastion to simplify key management.
# SSH host keys should be verified automatically via DNS for the bastion
# If you don't have native IPv6 you must proxy through access-vk.yoctoproject.org.
Host *-vk-*.yocto.io
ProxyJump access-vk.yoctoproject.org
#User [username]
#IdentityFile /home/[username]/.ssh/id_rsa
# We don't need strict checking on the private network.
StrictHostKeyChecking no
VisualHostKey no
# Don't bother saving hostkeys we don't check
UserKnownHostsFile /dev/null

===Verify Fingerprints===
Now actually ssh to access.yoctoproject.org and verify that the fingerprint you receive matches a fingerprint below.

access-vk.yoctoproject.org
ED25519 key fingerprint is SHA256:eDGzlYP3G+io9ylXmE6HMwtLMJ3eV82DveBnbM2mgJo.

===Connect!===
Now that you've added access.yoctoproject.org to your known hosts you don't need to worry about fingerprints anymore. Time to connect to a builder. Run:
ssh debian12-vk-1.yocto.io

If all worked correctly you are now logged in. Build workers are [https://autobuilder.yoctoproject.org/typhoon/#/workers listed on the controller]. Append .yocto.io to the name to ssh.

===Need to work on the build scripts?===
If you are on the SWAT team you can access pokybuild using this sudo command:
sudo -iu pokybuild

keywords: ssh access auto builder accessing autobuilders

User talk:Andrew.bradford

2024-11-08T19:15:22Z

MichaelHalstead: Welcome!

User:Andrew.bradford

2024-11-08T19:15:22Z

MichaelHalstead: Creating user page for new user.

Embedded Software Engineer at Konsulko Group

User talk:Red33

2024-10-11T18:25:58Z

MichaelHalstead: Welcome!

User:Red33

2024-10-11T18:25:58Z

MichaelHalstead: Creating user page for new user.

Embedded software developer since 2007, on yocto since 2012.

User talk:Azzentys

2024-10-02T16:51:41Z

MichaelHalstead: Welcome!

User:Azzentys

2024-10-02T16:51:41Z

MichaelHalstead: Creating user page for new user.

- Junior software engineer working on some cool BSP projects at my day job.
- Enjoy working on bootloaders, kernel and building distributions using yocto project.

Accessing Autobuilders

2024-09-27T00:15:59Z

MichaelHalstead: /* Configure ssh */

==Connecting to Autobuilders==
We use an ssh jumphost called access.yoctoproject.org/access.yocto.io to connect to the autobuilders. Jumphosts enhance security by removing the threat of hijacked ssh-agents and limiting the services running on Internet exposed hosts.

===Generate keys===
In order to access any of the autobuilders your ssh public keys must first be installed. The preferred key type is ECC. RSA with 4096 bits is also acceptable. Please put your e-mail, the date of generation, and the host the key lives on in the comment. Please set a passphrase even if it's a simple one! Ideally your private key will never leave the host it is generated on - so if you have multiple machines please generate multiple keys. E-mail your '''public''' key named ~/.ssh/id_ed25519.pub or id_rsa.pub to helpdesk@yoctoproject.org. Keep id_ed25519 or id_rsa(the private key) super safe. Please never share it with anyone or copy it onto the Internet. Don't e-mail it to yourself either.

ssh-keygen -t ed25519 -C "your_email@example.com_2012-05-30_localhostname"

Substitute your own e-mail and your computer's hostname in the command above. Setting these helps with troubleshooting in the future.

===Configure ssh===
Edit ~/.ssh/config on your local machine and add:

Host access.yoctoproject.org access-vk.yoctoproject.org
# Make sure your username matches your account on the autobuilder
#User [username]
# Give the full path to the proper public key if needed
#IdentityFile /home/[username]/.ssh/id_rsa
# If your network requires you to use a SOCKS proxy enable it here
# ProxyCommand nc -X5 -x [proxyserver.address.company.com:1080] %h %p
# If your system uses 'ncat', rather than 'netcat', use these options to enable a SOCKS proxy
# ProxyCommand nc --proxy-type socks5 --proxy [proxyserver.address.company.com:1080] %h %p

# Typhoon workers are on a private network. Proxy through the bastion.
Host *-ty-*.yocto.io *-arm-*.yocto.io perf-*.yocto.io
ProxyJump access.yoctoproject.org
# Correct username and key repeated from above.
#User [username]
#IdentityFile /home/[username]/.ssh/id_rsa
# We don't need strict checking on the private network.
StrictHostKeyChecking no
VisualHostKey no
# Don't bother saving hostkeys we don't check
UserKnownHostsFile /dev/null

# Valkyrie proxy through a bastion to simplify key management.
# SSH host keys should be verified automatically via DNS
# If you don't have native IPv6 you must proxy through access-vk.yoctoproject.org.
Host *-vk-*.yocto.io
ProxyJump access-vk.yoctoproject.org
StrictHostKeyChecking no

===Verify Fingerprints===
Now actually ssh to access.yoctoproject.org and verify that the fingerprint you receive matches a fingerprint below.

access.yocto.io
256 SHA256:d3eQ8azExpEKfcJExpUSpgw9D7gZgVDZ6gl4Bt5r6cQ (ED25519)
256 SHA256:jKW/rkm3+bNdtJ5CepVyHsxnbY8T78hk7lLwB0or0uA (ECDSA)
2048 SHA256:Qpvu4aUBox4eaYTeneRx5zMjwKTsZrJnn5VS9N5w+Fo (RSA)

access-vk.yoctoproject.org
ED25519 key fingerprint is SHA256:eDGzlYP3G+io9ylXmE6HMwtLMJ3eV82DveBnbM2mgJo.

===Connect!===
Now that you've added access.yoctoproject.org to your known hosts you don't need to worry about fingerprints anymore. Time to connect to a builder. Run:
ssh centos8-ty-1.yocto.io

If all worked correctly you are now logged in. Build workers are [https://autobuilder.yoctoproject.org/typhoon/#/workers listed on the controller]. Append .yocto.io to the name to ssh.

===Need to work on the build scripts?===
If you are on the SWAT team you can access pokybuild using this sudo command:
sudo -iu pokybuild

keywords: ssh access auto builder accessing autobuilders

User talk:Agodard

2024-09-26T16:13:06Z

MichaelHalstead: Welcome!

User:Agodard

2024-09-26T16:13:06Z

MichaelHalstead: Creating user page for new user.

Maintainer for the Yocto Project documentation and engineer at Bootlin.

Accessing Autobuilders

2024-09-23T18:06:36Z

MichaelHalstead: /* Configure ssh */

==Connecting to Autobuilders==
We use an ssh jumphost called access.yoctoproject.org/access.yocto.io to connect to the autobuilders. Jumphosts enhance security by removing the threat of hijacked ssh-agents and limiting the services running on Internet exposed hosts.

===Generate keys===
In order to access any of the autobuilders your ssh public keys must first be installed. The preferred key type is ECC. RSA with 4096 bits is also acceptable. Please put your e-mail, the date of generation, and the host the key lives on in the comment. Please set a passphrase even if it's a simple one! Ideally your private key will never leave the host it is generated on - so if you have multiple machines please generate multiple keys. E-mail your '''public''' key named ~/.ssh/id_ed25519.pub or id_rsa.pub to helpdesk@yoctoproject.org. Keep id_ed25519 or id_rsa(the private key) super safe. Please never share it with anyone or copy it onto the Internet. Don't e-mail it to yourself either.

ssh-keygen -t ed25519 -C "your_email@example.com_2012-05-30_localhostname"

Substitute your own e-mail and your computer's hostname in the command above. Setting these helps with troubleshooting in the future.

===Configure ssh===
Edit ~/.ssh/config on your local machine and add:

Host access.yoctoproject.org access-vk.yoctoproject.org
# Make sure your username matches your account on the autobuilder
#User [username]
# Give the full path to the proper public key if needed
#IdentityFile /home/[username]/.ssh/id_rsa
# If your network requires you to use a SOCKS proxy enable it here
# ProxyCommand nc -X5 -x [proxyserver.address.company.com:1080] %h %p
# If your system uses 'ncat', rather than 'netcat', use these options to enable a SOCKS proxy
# ProxyCommand nc --proxy-type socks5 --proxy [proxyserver.address.company.com:1080] %h %p

# Typhoon workers are on a private network. Proxy through the bastion.
Host *-ty-*.yocto.io *-arm-*.yocto.io perf-*.yocto.io
ProxyJump access.yoctoproject.org
# Correct username and key repeated from above.
#User [username]
#IdentityFile /home/[username]/.ssh/id_rsa
# We don't need strict checking on the private network.
StrictHostKeyChecking no
VisualHostKey no
# Don't bother saving hostkeys we don't check
UserKnownHostsFile /dev/null

# Valkyrie proxy through a bastion to simplify key management.
# SSH host keys should be verified automatically via DNS
# If you don't have native IPv6 you must proxy through a dual-stack worker.
Host *-vk-*.yocto.io
ProxyJump access-vk.yoctoproject.org
StrictHostKeyChecking no

===Verify Fingerprints===
Now actually ssh to access.yoctoproject.org and verify that the fingerprint you receive matches a fingerprint below.

access.yocto.io
256 SHA256:d3eQ8azExpEKfcJExpUSpgw9D7gZgVDZ6gl4Bt5r6cQ (ED25519)
256 SHA256:jKW/rkm3+bNdtJ5CepVyHsxnbY8T78hk7lLwB0or0uA (ECDSA)
2048 SHA256:Qpvu4aUBox4eaYTeneRx5zMjwKTsZrJnn5VS9N5w+Fo (RSA)

access-vk.yoctoproject.org
ED25519 key fingerprint is SHA256:eDGzlYP3G+io9ylXmE6HMwtLMJ3eV82DveBnbM2mgJo.

===Connect!===
Now that you've added access.yoctoproject.org to your known hosts you don't need to worry about fingerprints anymore. Time to connect to a builder. Run:
ssh centos8-ty-1.yocto.io

If all worked correctly you are now logged in. Build workers are [https://autobuilder.yoctoproject.org/typhoon/#/workers listed on the controller]. Append .yocto.io to the name to ssh.

===Need to work on the build scripts?===
If you are on the SWAT team you can access pokybuild using this sudo command:
sudo -iu pokybuild

keywords: ssh access auto builder accessing autobuilders

Accessing Autobuilders

2024-09-23T17:11:12Z

MichaelHalstead:

==Connecting to Autobuilders==
We use an ssh jumphost called access.yoctoproject.org/access.yocto.io to connect to the autobuilders. Jumphosts enhance security by removing the threat of hijacked ssh-agents and limiting the services running on Internet exposed hosts.

===Generate keys===
In order to access any of the autobuilders your ssh public keys must first be installed. The preferred key type is ECC. RSA with 4096 bits is also acceptable. Please put your e-mail, the date of generation, and the host the key lives on in the comment. Please set a passphrase even if it's a simple one! Ideally your private key will never leave the host it is generated on - so if you have multiple machines please generate multiple keys. E-mail your '''public''' key named ~/.ssh/id_ed25519.pub or id_rsa.pub to helpdesk@yoctoproject.org. Keep id_ed25519 or id_rsa(the private key) super safe. Please never share it with anyone or copy it onto the Internet. Don't e-mail it to yourself either.

ssh-keygen -t ed25519 -C "your_email@example.com_2012-05-30_localhostname"

Substitute your own e-mail and your computer's hostname in the command above. Setting these helps with troubleshooting in the future.

===Configure ssh===
Edit ~/.ssh/config on your local machine and add:

Host access.yoctoproject.org access-vk.yoctoproject.org
# Make sure your username matches your account on the autobuilder
#User [username]
# Give the full path to the proper public key if needed
#IdentityFile /home/[username]/.ssh/id_rsa
# If your network requires you to use a SOCKS proxy enable it here
# ProxyCommand nc -X5 -x [proxyserver.address.company.com:1080] %h %p
# If your system uses 'ncat', rather than 'netcat', use these options to enable a SOCKS proxy
# ProxyCommand nc --proxy-type socks5 --proxy [proxyserver.address.company.com:1080] %h %p

# Typhoon workers are on a private network. Proxy through the bastion.
Host *-ty-*.yocto.io *-arm-*.yocto.io
ProxyJump access.yoctoproject.org
# Correct username and key repeated from above.
#User [username]
#IdentityFile /home/[username]/.ssh/id_rsa
# We don't need strict checking on the private network.
StrictHostKeyChecking no
VisualHostKey no
# Don't bother saving hostkeys we don't check
UserKnownHostsFile /dev/null

# Valkyrie proxy through a bastion to simplify key management.
# SSH host keys should be verified automatically via DNS
# If you don't have native IPv6 you must proxy through a dual-stack worker.
Host *-vk-*.yocto.io
ProxyJump access-vk.yoctoproject.org
StrictHostKeyChecking no

===Verify Fingerprints===
Now actually ssh to access.yoctoproject.org and verify that the fingerprint you receive matches a fingerprint below.

access.yocto.io
256 SHA256:d3eQ8azExpEKfcJExpUSpgw9D7gZgVDZ6gl4Bt5r6cQ (ED25519)
256 SHA256:jKW/rkm3+bNdtJ5CepVyHsxnbY8T78hk7lLwB0or0uA (ECDSA)
2048 SHA256:Qpvu4aUBox4eaYTeneRx5zMjwKTsZrJnn5VS9N5w+Fo (RSA)

access-vk.yoctoproject.org
ED25519 key fingerprint is SHA256:eDGzlYP3G+io9ylXmE6HMwtLMJ3eV82DveBnbM2mgJo.

===Connect!===
Now that you've added access.yoctoproject.org to your known hosts you don't need to worry about fingerprints anymore. Time to connect to a builder. Run:
ssh centos8-ty-1.yocto.io

If all worked correctly you are now logged in. Build workers are [https://autobuilder.yoctoproject.org/typhoon/#/workers listed on the controller]. Append .yocto.io to the name to ssh.

===Need to work on the build scripts?===
If you are on the SWAT team you can access pokybuild using this sudo command:
sudo -iu pokybuild

keywords: ssh access auto builder accessing autobuilders

Accessing Autobuilders

2024-09-23T17:03:16Z

MichaelHalstead: /* Configure ssh */

==Connecting to Autobuilders==
We use an ssh jumphost called access.yoctoproject.org/access.yocto.io to connect to the autobuilders. Jumphosts enhance security by removing the threat of hijacked ssh-agents and limiting the services running on Internet exposed hosts.

===Generate keys===
In order to access any of the autobuilders your ssh public keys must first be installed. The preferred key type is ECC. RSA with 4096 bits is also acceptable. Please put your e-mail, the date of generation, and the host the key lives on in the comment. Please set a passphrase even if it's a simple one! Ideally your private key will never leave the host it is generated on - so if you have multiple machines please generate multiple keys. E-mail your '''public''' key named ~/.ssh/id_ed25519.pub or id_rsa.pub to helpdesk@yoctoproject.org. Keep id_ed25519 or id_rsa(the private key) super safe. Please never share it with anyone or copy it onto the Internet. Don't e-mail it to yourself either.

ssh-keygen -t ed25519 -C "your_email@example.com_2012-05-30_localhostname"

Substitute your own e-mail and your computer's hostname in the command above. Setting these helps with troubleshooting in the future.

===Configure ssh===
Edit ~/.ssh/config on your local machine and add:

Host access.yoctoproject.org access-vk.yoctoproject.org
# Make sure your username matches your account on the autobuilder
#User [username]
# Give the full path to the proper public key if needed
#IdentityFile /home/[username]/.ssh/id_rsa
# If your network requires you to use a SOCKS proxy enable it here
# ProxyCommand nc -X5 -x [proxyserver.address.company.com:1080] %h %p
# If your system uses 'ncat', rather than 'netcat', use these options to enable a SOCKS proxy
# ProxyCommand nc --proxy-type socks5 --proxy [proxyserver.address.company.com:1080] %h %p

# Typhoon workers are on a private network. Proxy through the bastion.
Host *-ty-*.yocto.io *-arm-*.yocto.io
ProxyJump access.yoctoproject.org
# Correct username and key repeated from above.
#User [username]
#IdentityFile /home/[username]/.ssh/id_rsa
# We don't need strict checking on the private network.
StrictHostKeyChecking no
VisualHostKey no
# Don't bother saving hostkeys we don't check
UserKnownHostsFile /dev/null

# Valkyrie proxy through a bastion to simplify key management.
# If you don't have native IPv6 you must proxy through a dual-stack worker.
Host *-vk-*.yocto.io
ProxyJump access-vk.yoctoproject.org
StrictHostKeyChecking no

===Verify Fingerprints===
Now actually ssh to access.yoctoproject.org and verify that the fingerprint you receive matches a fingerprint below.

access.yocto.io
256 SHA256:d3eQ8azExpEKfcJExpUSpgw9D7gZgVDZ6gl4Bt5r6cQ (ED25519)
256 SHA256:jKW/rkm3+bNdtJ5CepVyHsxnbY8T78hk7lLwB0or0uA (ECDSA)
2048 SHA256:Qpvu4aUBox4eaYTeneRx5zMjwKTsZrJnn5VS9N5w+Fo (RSA)

===Connect!===
Now that you've added access.yoctoproject.org to your known hosts you don't need to worry about fingerprints anymore. Time to connect to a builder. Run:
ssh centos8-ty-1.yocto.io

If all worked correctly you are now logged in. Build workers are [https://autobuilder.yoctoproject.org/typhoon/#/workers listed on the controller]. Append .yocto.io to the name to ssh.

===Need to work on the build scripts?===
If you are on the SWAT team you can access pokybuild using this sudo command:
sudo -iu pokybuild

keywords: ssh access auto builder accessing autobuilders

Accessing Autobuilders

2024-09-23T16:45:54Z

MichaelHalstead: /* Configure ssh */

==Connecting to Autobuilders==
We use an ssh jumphost called access.yoctoproject.org/access.yocto.io to connect to the autobuilders. Jumphosts enhance security by removing the threat of hijacked ssh-agents and limiting the services running on Internet exposed hosts.

===Generate keys===
In order to access any of the autobuilders your ssh public keys must first be installed. The preferred key type is ECC. RSA with 4096 bits is also acceptable. Please put your e-mail, the date of generation, and the host the key lives on in the comment. Please set a passphrase even if it's a simple one! Ideally your private key will never leave the host it is generated on - so if you have multiple machines please generate multiple keys. E-mail your '''public''' key named ~/.ssh/id_ed25519.pub or id_rsa.pub to helpdesk@yoctoproject.org. Keep id_ed25519 or id_rsa(the private key) super safe. Please never share it with anyone or copy it onto the Internet. Don't e-mail it to yourself either.

ssh-keygen -t ed25519 -C "your_email@example.com_2012-05-30_localhostname"

Substitute your own e-mail and your computer's hostname in the command above. Setting these helps with troubleshooting in the future.

===Configure ssh===
Edit ~/.ssh/config on your local machine and add:

# For Valkyrie
# If you don't have native IPv6 proxy through a dual-stack worker
Host *-vk-*arm*.yocto.io
ProxyJump debian12-vk-2.yocto.io

Host access.yoctoproject.org
# Make sure your username matches your account on the autobuilder
#User [username]
# Give the full path to the proper public key if needed
#IdentityFile /home/[username]/.ssh/id_rsa
# If your network requires you to use a SOCKS proxy enable it here
# ProxyCommand nc -X5 -x [proxyserver.address.company.com:1080] %h %p
# If your system uses 'ncat', rather than 'netcat', use these options to enable a SOCKS proxy
# ProxyCommand nc --proxy-type socks5 --proxy [proxyserver.address.company.com:1080] %h %p

# Typhoon workers are on a private network. Proxy through the bastion.
Host *-ty-*.yocto.io *-arm-*.yocto.io
ProxyJump access.yoctoproject.org
# Correct username and key repeated from above.
#User [username]
#IdentityFile /home/[username]/.ssh/id_rsa
# We don't need strict checking on the private network.
StrictHostKeyChecking no
VisualHostKey no
# Don't bother saving hostkeys we don't check
UserKnownHostsFile /dev/null

===Verify Fingerprints===
Now actually ssh to access.yoctoproject.org and verify that the fingerprint you receive matches a fingerprint below.

access.yocto.io
256 SHA256:d3eQ8azExpEKfcJExpUSpgw9D7gZgVDZ6gl4Bt5r6cQ (ED25519)
256 SHA256:jKW/rkm3+bNdtJ5CepVyHsxnbY8T78hk7lLwB0or0uA (ECDSA)
2048 SHA256:Qpvu4aUBox4eaYTeneRx5zMjwKTsZrJnn5VS9N5w+Fo (RSA)

===Connect!===
Now that you've added access.yoctoproject.org to your known hosts you don't need to worry about fingerprints anymore. Time to connect to a builder. Run:
ssh centos8-ty-1.yocto.io

If all worked correctly you are now logged in. Build workers are [https://autobuilder.yoctoproject.org/typhoon/#/workers listed on the controller]. Append .yocto.io to the name to ssh.

===Need to work on the build scripts?===
If you are on the SWAT team you can access pokybuild using this sudo command:
sudo -iu pokybuild

keywords: ssh access auto builder accessing autobuilders

User talk:Jstephan

2024-09-03T16:44:29Z

MichaelHalstead: Welcome!

User:Jstephan

2024-09-03T16:44:29Z

MichaelHalstead: Creating user page for new user.

I am an enthusiastic open source developer since I started computer science school. I currently works at Baylibre on the Linux kernel (mainly on camera support and iio-subsystem) and the Yocto Project, contributing back to upstream as much as possible, especially on the Yocto Project (bblock and devtool).

Yocto Project:Terms of Service

2024-07-29T23:42:15Z

MichaelHalstead: Old link is now a 404.

Please see https://wiki.yoctoproject.org/wiki/Community_Guidelines and https://www.yoctoproject.org/code-of-conduct/ for details.

User talk:Tmurugas

2024-07-29T23:36:57Z

MichaelHalstead: Welcome!

User:Tmurugas

2024-07-29T23:36:57Z

MichaelHalstead: Creating user page for new user.

I am a Linux OS Software Engineer

User talk:ReliableEmbeddedSystems

2024-07-29T23:36:36Z

MichaelHalstead: Welcome!

User:ReliableEmbeddedSystems

2024-07-29T23:36:36Z

MichaelHalstead: Creating user page for new user.

Reliable Embedded Systems – Robert Berger e.U. is a leading company that provides high-quality training and consulting services. Our mission is to help you improve your embedded software skills. We are committed to being a company of exceptional quality in every aspect of its business. We are convinced that great relationships with our customers, partners, and affiliations are very important for success.

Robert Berger is a well-known and recognized expert. He shares his knowledge by teaching about the Yocto Project®, Embedded Linux, and Real-Time on a mission to “yoctoize” the world “#yoctoizing” as well as supporting you to use containers with your embedded systems “#embcontainer“. Robert travels around Europe and helps companies worldwide via remote sessions.

Although people with varying levels of expertise join our public events, we manage to provide a solid foundation by bridging the gap between theory and practice.

Private workshops provide a more flexible course outline and allow us to focus on company and project-specific issues – consulting included.

There is no need to bring your own equipment. We will provide you with the same equipment during both on-site and remote training sessions.

User talk:Beroset

2024-07-29T23:34:39Z

MichaelHalstead: Welcome!

User:Beroset

2024-07-29T23:34:39Z

MichaelHalstead: Creating user page for new user.

I'm an embedded systems engineer with decades of experience.

Bugzilla Configuration and Bug Tracking

2024-07-26T18:59:04Z

MichaelHalstead: New bugzilla account creation guidelines.

You should also read our [[Community Guidelines]] before submitting bugs.

------
== Defect Management ==
Yocto uses '''[http://www.bugzilla.org/ Bugzilla]''' as its defect tracking tool.

=== Home Address ===
http://bugzilla.yoctoproject.org

=== Get an Account ===
Anyone working on the Yocto project can query existing bugs in Bugzilla. You must have an account to submit a bug, edit a bug, or take action on a bug.

To set up an account, email it-coreprojects-helpdesk@linuxfoundation.org with the subject "Yocto Project Bugzilla Account Request" and a one sentence description of your role in the project or the bug you intend to file or update. Self registration has to be disabled due to increasing spam attacks.

=== Classification, Product and Components ===
Yocto Bugzilla uses these Classifications, Products and Components. Configurations change over time and should be defined by module owners:

<pre>
+============================+===================================+=====================================================+
| Classification | Product | Components |
|================================================================+=====================================================|
| Build system, metadata & | BitBake | bitbake |
| Runtime | | |
| +-----------------------------------+-----------------------------------------------------|
| | BSPs | bsps-configuration |
| | +-----------------------------------------------------|
| | | bsps-intel-corei7-64 |
| | +-----------------------------------------------------|
| | | bsps-meta-fsl-arm |
| | +-----------------------------------------------------|
| | | bsps-meta-fsl-ppc |
| | +-----------------------------------------------------|
| | | bsps-meta-intel |
| | +-----------------------------------------------------|
| | | bsps-meta-minnow |
| | +-----------------------------------------------------|
| | | bsps-meta-ti |
| | +-----------------------------------------------------|
| | | bsps-meta-xilinx |
| | +-----------------------------------------------------|
| | | bsps-meta-yocto |
| | +-----------------------------------------------------|
| | | bsps-oe-core |
| | +-----------------------------------------------------|
| | | bsps-runtime |
| | +-----------------------------------------------------|
| | | bsps-tools |
| +-----------------------------------+-----------------------------------------------------|
| | Meta-yocto | configuration |
| | +-----------------------------------------------------|
| | | meta-yocto |
| +-----------------------------------+-----------------------------------------------------|
| | OE-Core | configuration |
| | +-----------------------------------------------------|
| | | connectivity |
| | +-----------------------------------------------------|
| | | core |
| | +-----------------------------------------------------|
| | | deployment |
| | +-----------------------------------------------------|
| | | devtools /tool chain |
| | +-----------------------------------------------------|
| | | graphics |
| | +-----------------------------------------------------|
| | | kernel |
| | +-----------------------------------------------------|
| | | multimedia |
| | +-----------------------------------------------------|
| | | Scripts and Tools |
| | +-----------------------------------------------------|
| | | virtual machines |
| +-----------------------------------+-----------------------------------------------------|
| | Other YP Layers | baryon |
| | +-----------------------------------------------------|
| | | layers |
| | +-----------------------------------------------------|
| | | meta-cgl |
| | +-----------------------------------------------------|
| | | meta-intel-iot-middleware |
| | +-----------------------------------------------------|
| | | meta-security |
| | +-----------------------------------------------------|
| | | meta-swupd |
| | +-----------------------------------------------------|
| | | meta-zephyr |
| +-----------------------------------+-----------------------------------------------------|
| | Runtime | build-appliance |
| +-----------------------------------+-----------------------------------------------------|
| | Security - Recipe Upgrade | security |
| +-----------------------------------+-----------------------------------------------------|
| | Toaster | toaster |
+----------------------------+-----------------------------------+-----------------------------------------------------|
| Yocto Project Subprojects | ADT | adt |
| | +-----------------------------------------------------|
| | | kernel analysis |
| +-----------------------------------+-----------------------------------------------------|
| | Automated Update Handler | Automatic Update Handler |
| +-----------------------------------+-----------------------------------------------------|
| | CROPS | crops-default |
| | +-----------------------------------------------------|
| | | eclipse-crops |
| +-----------------------------------+-----------------------------------------------------|
| | Cross-prelink | cross-prelink |
| | +-----------------------------------------------------|
| | | poky integration |
| +-----------------------------------+-----------------------------------------------------|
| | Eclipse Plugin | eclipse-plugin |
| +-----------------------------------+-----------------------------------------------------|
| | Error Reporting Tool | Error Reporting Tool |
| +-----------------------------------+-----------------------------------------------------|
| | eSDK | eSDK |
| +-----------------------------------+-----------------------------------------------------|
| | IoT Reference OS Kit | intel-iot-refkit-application-support |
| | +-----------------------------------------------------|
| | | intel-iot-refkit-connectivity |
| | +-----------------------------------------------------|
| | | intel-iot-refkit-default |
| | +-----------------------------------------------------|
| | | intel-iot-refkit-documentation |
| | +-----------------------------------------------------|
| | | intel-iot-refkit-multimedia |
| | +-----------------------------------------------------|
| | | intel-iot-refkit-platform-support |
| | +-----------------------------------------------------|
| | | intel-iot-refkit-profile-computer-vision |
| | +-----------------------------------------------------|
| | | intel-iot-refkit-profile-gateway |
| | +-----------------------------------------------------|
| | | intel-iot-refkit-profile-industrial-robotics |
| | +-----------------------------------------------------|
| | | intel-iot-refkit-security |
| | +-----------------------------------------------------|
| | | intel-iot-refkit-software-update |
| | +-----------------------------------------------------|
| | | intel-iot-refkit-tools |
| +-----------------------------------+-----------------------------------------------------|
| | Kernel | kernel-configuration |
| | +-----------------------------------------------------|
| | | kernel-tooling |
| | +-----------------------------------------------------|
| | | linux-yocto |
| +-----------------------------------+-----------------------------------------------------|
| | Layer Index | Layer Index |
| | +-----------------------------------------------------|
| | | Layer Index Metadata |
| +-----------------------------------+-----------------------------------------------------|
| | Matchbox | matchbox |
| +-----------------------------------+-----------------------------------------------------|
| | opkg | opkg |
| +-----------------------------------+-----------------------------------------------------|
| | Patchwork/Patchtest | Patchtest |
| | +-----------------------------------------------------|
| | | Patchtest Testsuite |
| | +-----------------------------------------------------|
| | | Patchwork |
| +-----------------------------------+-----------------------------------------------------|
| | Pseudo | poky integration |
| | +-----------------------------------------------------|
| | | pseudo |
| +-----------------------------------+-----------------------------------------------------|
| | Recipe Reporting System (RRS) | Recipe Reporting System (RRS) |
| +-----------------------------------+-----------------------------------------------------|
| | Sato | gtk-engine |
| | +-----------------------------------------------------|
| | | Icon |
| | +-----------------------------------------------------|
| | | Matchbox |
| | +-----------------------------------------------------|
| | | sato |
+----------------------------+-----------------------------------+-----------------------------------------------------|
| Documentation | ADT Manual | SDK |
| +-----------------------------------+-----------------------------------------------------|
| | BitBake User Manual | bitbake-manual |
| +-----------------------------------+-----------------------------------------------------|
| | BSP Guide | bsp-docs |
| +-----------------------------------+-----------------------------------------------------|
| | Demos | demos-docs |
| +-----------------------------------+-----------------------------------------------------|
| | Development Manual | devolopment |
| +-----------------------------------+-----------------------------------------------------|
| | General Docs | docs-general |
| +-----------------------------------+-----------------------------------------------------|
| | Kernel Development | kernel-development |
| +-----------------------------------+-----------------------------------------------------|
| | Mega Manual | mega-manual |
| +-----------------------------------+-----------------------------------------------------|
| | Profile and Tracing Manual | profile-manual |
| +-----------------------------------+-----------------------------------------------------|
| | Quick Start | quick-start |
| +-----------------------------------+-----------------------------------------------------|
| | Reference | handbook |
| | +-----------------------------------------------------|
| | | PRD |
+----------------------------+-----------------------------------+-----------------------------------------------------|
| Infrastructure | AutoBuilder | autobuilder |
| | +-----------------------------------------------------|
| | | jenkins autobuilder plugin |
| +-----------------------------------+-----------------------------------------------------|
| | Bugzilla | bugzilla |
| +-----------------------------------+-----------------------------------------------------|
| | Program Management | management-default |
| +-----------------------------------+-----------------------------------------------------|
| | Release Process | Release Process |
| +-----------------------------------+-----------------------------------------------------|
| | Testopia | testopia |
| +-----------------------------------+-----------------------------------------------------|
| | Website | web-admin |
| | +-----------------------------------------------------|
| | | web-content |
| | +-----------------------------------------------------|
| | | web-design |
| | +-----------------------------------------------------|
| | | web-structure |
| +-----------------------------------+-----------------------------------------------------|
| | Wiki | wiki |
+----------------------------+-----------------------------------+-----------------------------------------------------|
| QA/Testing | Automated Build Testing | automated-build-testing |
| +-----------------------------------+-----------------------------------------------------|
| | Automated Runtime Testing | automated-runtime-testing |
| +-----------------------------------+-----------------------------------------------------|
| | IoT Reference OS Kit Testing | intel-iot-refkit-automated-build-testing |
| | +-----------------------------------------------------|
| | | intel-iot-refkit-automated-runtime-testing |
| | +-----------------------------------------------------|
| | | intel-iot-refkit-manual-testing |
| +-----------------------------------+-----------------------------------------------------|
| | Manual Testing | manual-testing |
| +-----------------------------------+-----------------------------------------------------|
| | Test Plans/Suite | test-plans/suite |
+----------------------------+-----------------------------------+-----------------------------------------------------|
| Runtime | General Runtime | General Runtime |
| +-----------------------------------+-----------------------------------------------------|
| | Installation | Installation |
| +-----------------------------------+-----------------------------------------------------|
| | Package Management Issues | Debian Packaging - DEB |
| | +-----------------------------------------------------|
| | | ipkg opkg |
| | +-----------------------------------------------------|
| | | package-management-issues |
| | +-----------------------------------------------------|
| | | RPM |
| +-----------------------------------+-----------------------------------------------------|
| | Security | security |
| +-----------------------------------+-----------------------------------------------------|
| | System Startup | system-startup |
+============================|===================================+=====================================================+
</pre>

=== Platform ===
This field represents the hardware and architecture (platform) for which the bug applies. The platform consists of a Hardware component and an Architecture component. For example, the Platform could have a hardware of "PC" and an architecture of "x86". Here is a list of the hardware choices:

* All
* PC
* Beagleboard
* BeagleBone
* Blacksand
* Cheifriver
* Crownbay
* E-Menlow
* EdgeRouter
* FRI2
* Galileo
* JasperForest
* MinnowBoard
* MinnowBoard Max
* mpc8315e-rdb
* Netbook
* NUC
* RouterStationpro
* TunnelCreek
* Macintosh
* Other

Here is a list of the Architecture choices:

* Multiple
* arm
* arm64
* mips
* mips64
* ppc
* ppc64
* x86
* x86_64
* Other

=== Version ===
This field represents the version of the Yocto Project for which the bug applies. The list of versions can vary depending on the Classification, Component and Project. The list also contains versions of the Yocto Project that are currently being developed.

Here is a sample list of selections at given the last time this wiki page was updated:

* 2.0.3
* 2.0.4
* 2.1.2
* 2.1.3
* 2.1.4
* 2.2
* 2.2.1
* 2.2.2
* 2.2.3
* 2.3
* 2.3.1
* 2.3.2
* 2.4
* 2.5
* Unspecified

=== Target Milestone ===
This field represents the Yocto Project release milestone the assignee of the bug estimates the bug will be fixed. The values are based on releases and Milestone numbers. For example, "2.4 M4" indicates the fourth milestone for the 2.4 release.

=== Importance ===
The Importance of the bug is defined by its Priority and Severity. The Priority classifies the bug's fixing order. In other words, how soon will it get fixed relative to other bugs? Priorities are set during the bug Triage meeting and cannot be changed by the user. The priority appears to the left of the Severity field. Here are the values that Priority can be set to during the Triage meeting:

* High -- Bug fixing is planned immediately for the target milestone. Milestone cannot be released if there is a high bug opened against the milestone. High priority issues cause major functional loss of a specific feature that is POR for the up-comping milestone. These issues are easily hit by the user and greatly impact the user experience or customer requirements. Finally, these issues could be urgent security fixes that need to be corrected in a prior release. The bug assignee is not to change the target milestones for High bugs without prior approval of the Triage team.
* Medium+ -- Bug fixing is planned before the milestone and must be fixed or have a solution planned before the release is finalized. These issues are not show-stoppers but have somewhat significant impact to system functions and user experience.
* Medium -- These are important issues we keep track and try to plan fixing for the release. They have limited impact for the system functions and releases.
* Low -- Bug fixing is only done opportunistically. Generally not planned for the up-coming project release. Issues that are not a POR feature request, or are hard to reproduce fall into this category.
* Undecided -- These issues are newly reported and are '''undecided''' before Triage. Issues that are a feature request, which isn't approved for future release yet. This issue will be changed to have an actual Priority after the Triage team approves it.

'''Note:''' High impact but Low Priority bugs can be documented in the release notes.

The Severity indicates how much the issue impacted the person reporting the bug. Severity can be categorized into five areas.
* Critical -- Crashes, hang, loss of data, negative impact to other components, memory leak etc.
* Major -- Major loss of functionality of POR.
* Normal -- Regular issue, some loss of functionality under certain circumstance. This is the '''default''' Severity.
* Minor -- Minor loss of functionality, or issues with easy workaround available.
* Enhancement -- Request for enhancement or new feature to be worked.

=== Bug Status ===
* NEW -- A new reported bug with default assignee.
* ACCEPTED-- The assigned developer has reviewed and accept the bug.
* RESOLVED -- bug is fixed or closed by other resolved method.
** FIXED -- This is fixed and in the master branch will be set automatically during build
** NOTABUG -- This is verified as not a bug
** WONTFIX -- We will not fix this bug, possibly because a newer package fixes it.
** DUPLICATE -- Duplicate of another bug, possibly different failure mode
** INVALID -- The bug is invalid, sometimes this is used when the author of the bug does not provide accurate information, these will be reviewed by Triage team, and could be changed to '''NEEDINFO''' or it is not a feature of Yocto Project to fix.
** OBSOLETE -- The bug is obsolete, old bug that is no longer appropriate, or a package that is depercated.
** WORKSFORME -- The bug does not appear when tested by engineer, more appropriately, this may be '''NEEDINFO'''
* VERIFIED -- bug is double checked and agreed with the resolved method by original reporter.
* REOPENED: bug can be reopened, if it is in Resolved, Verified or Close stage.
* NEEDINFO: bug needs further information from someone in order to make progress on the bug. Whoever set a bug to NEEDINFO should also change the assignee to who they are requesting the information from.
* '''CLOSED''' stage is not used in normal bug life. When reported two same bugs by wrongly click button twice, the 2nd one can be closed. Generally it (close stage) is just for keeping wrong bug out of scrub cycle and statistic.

=== Bug Life Cycle ===
A normal Bug's life is starts from '''NEW''' and ends with '''VERIFIED'''. Triage team will select "verified: Program Management", after confirm the verification.

[[Image:Yocto_Bug_Life_Cycle.jpg|frame|none|Bug Life Cycle]]

Bug should be marked as '''RESOLVED/FIXED''', after its fixing patch is built into formal build (weekly build or milestone build). There is an automatic method to update bugs to '''RESOVLED/FIXED''' status by following steps.
# Developer fixed bug and check in patch to his ''contrib'' branch with special words in commit description (e.g. '''[YOCTO #4321]''')
# Developer asked tree gatekeeper to pull patch.
# Release Engineer do formal build. The build script will read new commit description and find out bug ID.
# Build script will notify bugzilla and update bugs status to '''RESOLVE/FIXED'''

If a weekly build includes a new commit, which reverts another patch, there should be a tool to judge whether the reverted patch summary include any bug fixing ID. If the reverted patch does include any bug fixing, the bug should be reopened.

[[Image:Yocto_Bug_Fix_Process.PNG|frame|none|Bug Fixing Process]]

== Submitting and Owning a Defect ==
Anyone working with Yocto who has a Bugzilla account can enter a defect. Bug submission should include severity, thorough environment information, proper and clear reproduce steps and logs.

=== Bug Submitter ===
When you submit (open) a bug, be sure to do the following:

# Provide a clear and simple bug subject. It is recommended to put a '''Fault Component Name''' with brackets at the beginning of subject as a keyword, e.g. [Poky].
# Validate all fields are correct. If fields are not filled out correctly, the bug might be sent back to the submitter.
# Judge and select the appropriate Severity.
# Add any additional information from the bug scrub.
# Assign the bug to the correct person to disposition the bug.
# If a bug is too vague to make a determination, then the Resolution Field of the bug will be set to '''NEEDINFO''' and sent back the bug submitter.
# Make sure you edit the '''CC''' list to include other people you might think should know about the defect.
# Set the "Documentation change" field appropriately. This field helps the people that create and maintain the Yocto Project manuals by alerting them to a documentation need for the defect's resolution.

'''NOTE:''' You cannot set a defect's Priority when you submit a bug. The Priority is set during the Bug Triage.

=== Bug Owner ===
If you are the owner of a bug, be sure to do the following:

# Review your bugs to check if there is enough information. If not, set the bug to '''NEEDINFO'''.
# Try to reproduce your bugs when clear steps exist in the bug's description.
# Address bugs based on their Priority and Severity. For example, High Priority bugs usually should be fixed in 2 weeks. High/critical bugs should be fixed as soon as possible, which impacts the whole system.
# Be timely regarding updating bugs with comments. Timely comments both helps those working on the bug and keeps a bug active. Set the bug to '''FIXED''' and provide the tree/commit information once the bug is fixed. You should not mark a bug as '''RESOLVED/FIXED''', if the patch is not checked into the repository.

== Bug Tracking ==
Because the Yocto Project spans many geographies and is a large and active project, a single bug scrub meeting is not easy to maintain. Consequently, a ''Triage'' is used to effectively disposition bugs. The Bug Triage team reviews a bug's severity and features and then schedules the bug to best facilitate a resolution. The Triage team sets new bug priorities, corrects ownership for the work to be done, and ensures an appropriate target milestone for the bug. The Triage process is documented at [[Bug_Triage]].

Part of the Triage process is the distribution of a weekly Bugzilla Cleanup Request. This email request is a reminder for bug owners when various parameters of a bug are not in line with the Yocto Project Bugzilla tracking system. For example, if a bug has no estimate information or milestone by which it should complete. Following is a summary of the type of information in the weekly Bugzilla Cleanup Request. For the actual request, links to lists of bugs exist that allow you to see the list of bugs that fail to meet a particular requirement:

*'''No Estimate:''' You own a medium or higher priority bug or enhancement in Bugzilla targeted for completion in the given release. Do to the amount of work trying to get done in Yocto Project, we are asking you take a minute or two and give an estimated amount of work – in "Perfect-Work-Days" – to complete the bug or enhancement. We know your estimates might not be perfect. However, this effort helps us know who is overloaded with work and where to apply the resources we have on the project. Please estimate how many "Perfect-Work-Days" remain to close the bugs in the "Estimate: Person-Days" box in Bugzilla. Also while updating the bug or enhancement, please ensure the estimate targets the correct Milestone for completion.

*'''Old Milestone:''' You are assigned an open bug in the Yocto Project Bugzilla tracker whose assigned milestone is old. To see the list of bugs with old milestones please look here: https://wiki.yoctoproject.org/wiki/Bug_Triage#Old_Milestone. Since the milestone for this bug in the Yocto Project has already passed, please do one of the following actions:
**If it is completed: Close the bug. (Great News!)
**If it is partly complete: Break the bug request into two or more parts and close what is done and move the remaining parts to a future milestone.
**If it is not done at all but you still plan to fix it in the future: Move the bug to milestone that is not yet completed. (Future is a possible milestone.)
**If it is no longer in your plans to do this but you think this still needs to be fixed: Change the bug to an unassigned priority. During the Triage process, we will assess the bug again and appropriately reassign the bug.
**If it no longer makes sense to fix this bug: Please close the bug request with a status of either OBSOLETE or WONTFIX.

*'''Needs specific milestone:''' You are assigned an open bug or enhancement in the Yocto Project Bugzilla tracker that has a medium+ or high priority assigned to it without a targeted specific milestone or specific dot release. All open medium+ or high bugs must have a specific target milestone or specific dot release assigned to them (e.g. 2.2.3). Medium+ and High bugs are not allowed to be set to the "Future" milestone but can be set to the milestone 2.99 which time to complete is still TBD.

*'''Needs to be broken up:''' You are assigned an open bug or enhancement in the Yocto Project Bugzilla tracker that is a medium or higher priority and has more than five "Perfect-Work-Days" assigned. All open medium or higher bugs with more than five days should be broken into smaller dependent tasks. If this is not possible please contact the Yocto Project program manager with bug number and an explanation of why it can't be broken into small tasks.

*'''Dependency Issue:''' You have a dependency problem in Yocto Project Bugzilla tracker where either your bug or enhancement is dependent on a lower priority bug or enhancement, or your bug or enhancement has a target milestone earlier than dependent bugs or enhancements. Please open your bug and review the dependencies to see what the problem is with the bug.

*'''Need Info > 2 Weeks:''' You have bugs or requested enhancements for the Yocto Project for which more information has been requested in order to allow progress on these bugs. These bugs or enhancements have been in this state waiting for this information from you for at least two weeks. Please update the bug or enhancement request at: https://wiki.yoctoproject.org/wiki/Bug_Triage#NEEDINFO to have the requested information so that work on this bug or enhancement can move forward. If you cannot supply the information, please change the bug's status to CLOSED and the resolution to either OBSOLETE or WONTFIX, whichever is more appropriate.

== Feature Request Process ==
New feature request should be applied through Bugzilla as a bug. User should set the Severity to Enhancement. The request will be triaged in the Triage Team meetings.

There will be two important feature request review time per year in March and September (2 months before final release). In the review period, there will be 2~4 times review meetings by the triage team. The Triage team will which decide new features which will be included in next release, that will be released in April and October.

User talk:NgWengMun Intel

2024-07-18T17:43:24Z

MichaelHalstead: Welcome!

User:NgWengMun Intel

2024-07-18T17:43:24Z

MichaelHalstead: Creating user page for new user.

I am currently working in Intel for open source yocto projects.

User talk:Skokkonda

2024-07-02T16:44:17Z

MichaelHalstead: Welcome!

User:Skokkonda

2024-07-02T16:44:17Z

MichaelHalstead: Creating user page for new user.

Contributing to open source and Yocto project.

User talk:Jookia

2024-06-28T05:35:52Z

MichaelHalstead: Welcome!

User:Jookia

2024-06-28T05:35:52Z

MichaelHalstead: Creating user page for new user.

I am Jookia, an embedded developer