|
|
(23 intermediate revisions by 2 users not shown) |
Line 12: |
Line 12: |
| !BitBake branch | | !BitBake branch |
| |- | | |- |
| |Pyro | | |CodeName |
| |2.3 | | |2.4 |
| |May 2017 | | |Fall 2017 |
| | | | | |
| |Development | | |Development |
| |
| |
| | | | | |
| |- | | |- |
| | |Pyro |
| | |2.3 |
| | |May 2017 |
| | |2.3.0 |
| | |Stable |
| | |17.0 |
| | |1.34 |
| |- | | |- |
| |Morty | | |Morty |
Line 167: |
Line 173: |
| |} | | |} |
|
| |
|
| '''Note:''' see also [[Stable branch maintenance]], [[Linux Yocto]], and [[Planning]] wiki's. | | '''Note:''' see also [[Stable branch maintenance]], [[Linux Yocto]], [[Planning]] and [[Release Feature Table]] pages. |
|
| |
|
| == Releases Links== | | == Releases Links== |
Line 329: |
Line 335: |
| | | | | |
| |} | | |} |
|
| |
| == Feature Table ==
| |
|
| |
| {| class="wikitable" border="2"
| |
| !Yocto Project Version
| |
| !Release Date
| |
| !Codename
| |
| !Feature
| |
| !Stablity
| |
| !Completness
| |
| !Documentation
| |
| !Plans
| |
| |-
| |
| |2.3
| |
| |May 2017
| |
| |Pyro
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |-
| |
| |-
| |
| |2.2
| |
| |Nov 2016
| |
| |Morty
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |-
| |
| |-
| |
| |2.1
| |
| |Apr 2016
| |
| |Krogoth
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |-
| |
| |-
| |
| |2.0
| |
| |Nov 2015
| |
| |Jethro
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |-
| |
| |-
| |
| |1.8
| |
| |Apr 2015
| |
| |Fido
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |-
| |
| |-
| |
| |1.7
| |
| |Oct 2014
| |
| |Dizzy
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |-
| |
| |-
| |
| |1.6
| |
| |Apr 2014
| |
| |Daisy
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |-
| |
| |-
| |
| |1.5
| |
| |Oct 2013
| |
| |Dora
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |-
| |
| |-
| |
| |1.4
| |
| |Apr 2013
| |
| |Dylan
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |-
| |
| |-
| |
| |1.3
| |
| |Oct 2012
| |
| |Danny
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |-
| |
| |-
| |
| |1.2
| |
| |Apr 2012
| |
| |Denzil
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |-
| |
| |-
| |
| |1.1
| |
| |Oct 2011
| |
| |Edison
| |
| |Multilibs & OE-core config - This work, which began in Yocto Project 1.0, needs to be completed.
| |
| Improve ease of BSP creation - Document the lifecycle and process. Possibly create walkthroughs or tutorials to integrate a new board into the linux-yocto kernel.
| |
| Enable users to easily and seamlessly build Yocto images - This refers to the effort to complete and integrate the Image Creator work started in 1.0.
| |
| Build performance – Get to the goal of 1 hour build time on a developer machine.
| |
| Upstreaming – Submit patches to upstream projects in order to reduce the large number of patches which are currently part of Yocto Project.
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |-
| |
| |-|1.1
| |
| |Oct 2011
| |
| |Edison
| |
| |Multilibs & OE-core config - This work, which began in Yocto Project 1.0, needs to be completed.
| |
| Improve ease of BSP creation - Document the lifecycle and process. Possibly create walkthroughs or tutorials to integrate a new board into the linux-yocto kernel.
| |
| Enable users to easily and seamlessly build Yocto images - This refers to the effort to complete and integrate the Image Creator work started in 1.0.
| |
| Build performance – Get to the goal of 1 hour build time on a developer machine.
| |
| Upstreaming – Submit patches to upstream projects in order to reduce the large number of patches which are currently part of Yocto Project.
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |-
| |
| |-|1.1
| |
| |Oct 2011
| |
| |Edison
| |
| |Multilibs & OE-core config - This work, which began in Yocto Project 1.0, needs to be completed.
| |
| Improve ease of BSP creation - Document the lifecycle and process. Possibly create walkthroughs or tutorials to integrate a new board into the linux-yocto kernel.
| |
| Enable users to easily and seamlessly build Yocto images - This refers to the effort to complete and integrate the Image Creator work started in 1.0.
| |
| Build performance – Get to the goal of 1 hour build time on a developer machine.
| |
| Upstreaming – Submit patches to upstream projects in order to reduce the large number of patches which are currently part of Yocto Project.
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |-
| |
| |-|1.1
| |
| |Oct 2011
| |
| |Edison
| |
| |Multilibs & OE-core config - This work, which began in Yocto Project 1.0, needs to be completed.
| |
| Improve ease of BSP creation - Document the lifecycle and process. Possibly create walkthroughs or tutorials to integrate a new board into the linux-yocto kernel.
| |
| Enable users to easily and seamlessly build Yocto images - This refers to the effort to complete and integrate the Image Creator work started in 1.0.
| |
| Build performance – Get to the goal of 1 hour build time on a developer machine.
| |
| Upstreaming – Submit patches to upstream projects in order to reduce the large number of patches which are currently part of Yocto Project.
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |-
| |
| |-|1.1
| |
| |Oct 2011
| |
| |Edison
| |
| |Multilibs & OE-core config - This work, which began in Yocto Project 1.0, needs to be completed.
| |
| Improve ease of BSP creation - Document the lifecycle and process. Possibly create walkthroughs or tutorials to integrate a new board into the linux-yocto kernel.
| |
| Enable users to easily and seamlessly build Yocto images - This refers to the effort to complete and integrate the Image Creator work started in 1.0.
| |
| Build performance – Get to the goal of 1 hour build time on a developer machine.
| |
| Upstreaming – Submit patches to upstream projects in order to reduce the large number of patches which are currently part of Yocto Project.
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |-
| |
| |-
| |
| |1.0
| |
| |Apr 2011
| |
| |Barnard
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |-
| |
| |-
| |
| }
| |