https://wiki.yoctoproject.org/wiki/api.php?action=feedcontributions&user=BillMills&feedformat=atomYocto Project - User contributions [en]2024-03-29T00:26:50ZUser contributionsMediaWiki 1.39.5https://wiki.yoctoproject.org/wiki/index.php?title=The_Yocto_Autobuilder&diff=85917The Yocto Autobuilder2023-09-07T18:15:51Z<p>BillMills: Fix my fix. Changed the wrong URL</p>
<hr />
<div>== The Yocto AutoBuilder ==<br />
<br />
The autobuilder '''[https://autobuilder.yoctoproject.org/typhoon/#/console Main Console]'''.<br />
<br />
The Yocto AutoBuilder is a buildbot (currently 3.x) based autobuilder implementation that can be used to build out and test custom distros utilizing OE-Core (either bare or through the poky repository)<br />
<br />
The source code can be downloaded from the '''[http://git.yoctoproject.org/cgit/cgit.cgi/yocto-autobuilder2/ yocto-autobuilder2]''' and '''[http://git.yoctoproject.org/cgit/cgit.cgi/yocto-autobuilder-helper/ yocto-autobuilder-helper]''' repositories.<br />
<br />
For details on the design and configuration of the AutoBuilder, refer to the documentation in those repositories.<br />
<br />
The yocto-autobuilder maintainer is [[User:Rpurdie | Richard Purdie]] (RP on IRC). All patches to the yocto-autobuilder2 should be sent to yocto@yoctoproject.org with "[yocto-autobuilder2]" in the Subject line. Please CC: richard.purdie@linuxfoundation.org. The hardware is maintained by the Linux Foundation on behalf of the Yocto Project and for infrastructure issues, please contact Michael Halstead (halstead on IRC).<br />
<br />
'''NOTE: please use autobuilder2''', autobuilder is dead [1], buildbot eight (aka 0.8.x) is dead.<br />
<br />
[1] http://git.yoctoproject.org/cgit.cgi/yocto-autobuilder/commit/?id=1369545f9819537535e4ab6ebeb49e7b173a8366<br />
<br />
=== Scheduled Builds ===<br />
<br />
The current active schedule can be seen in [https://git.yoctoproject.org/yocto-autobuilder2/tree/schedulers.py#n446 schedulers.py].<br />
<br />
The scheduled builds are:<br />
* a-quick on master every night on Monday to Saturday<br />
* a-full on master every Sunday night<br />
* metrics check each morning<br />
* check-layer for a number of meta-layers every night (master branch)<br />
* check-layer for a number of meta-layers one each night covering all active releases (spread over a week)<br />
* build performance checks 4 times a day on two distros<br />
* Auto Upgrade Helper twice a month<br />
* Doc rebuild on all branches for any commit that changes docs<br />
<br />
=== Starting Builds ===<br />
<br />
For autobuilder access, contact Michael Halstead <michael@yoctoproject.org> as an account is needed to start builds. These are usually available to stable branch maintainers or in special cases other layer maintainers for running builds on the project infrastructure. <br />
<br />
To start builds, from the main console you'd usually select 'a-quick' or 'a-full' from the top list of builders. If not logged in, login using the link on the top right of the page. You should then see a button "Start a-full build" or "Start a-quick build" which you can press. This opens a fairly complex form but in most cases you can use the "Release Shortcut Selector" to pre-populate the form with a given release's defaults. For a stable branch build on a test branch, you may then want to change the poky repository to point to poky-contrib and the branch to be the one you want to test. You should enter a reason for the build in the box at the top of the form. This is added to the [[BuildLog]] and us used by SWAT to decide what to do with bugs. When the form is correct, click "Start Build" at the bottom of the form.<br />
<br />
If making a release build, be sure to check all three check boxes, "Do we want to save build output?", "Generate a release?" and "Send QA alert emails?". The release milestone, release number and release rc number need to be filled in as appropriate too.<br />
<br />
The autobuilder can run multiple builds in parallel so builds can be queued as needed but please be sensible. The autobuilder users are usually around in #yp-infra on IRC which can be useful to schedule builds between us.<br />
<br />
The autobuilder maintenance window is morning for US PST on Fridays and builds should not be run over this period to allow weekly maintanance on the worker distros to be carried out.<br />
<br />
Autobuilder output for non-release builds is available at: https://autobuilder.yocto.io/pub/non-release/ and for release builds: https://autobuilder.yocto.io/pub/releases/.<br />
<br />
=== Autobuilder Build User Guidelines/Conditions of Use ===<br />
<br />
If you have the ability to run autobuilder builds there are some things you need to be mindful of:<br />
<br />
* It is expected that normally users should have resolved minor issues and done some testing before using the project infrastructure.<br />
* You are expected to triage the results of your own build<br />
* If you see unexplained failures, it is expected that bugs are filed for these, or where there are existing bugs, the bug should be updated. Please include which host/worker the build failed on. This allows triage to know which issues are occurring, their frequency and patterns like which host(s) they occur on.<br />
* The maintenance window is on Friday mornings US pacific time. Please do not start builds until maintenance is complete or run builds which wouldn't finish before maintenance is due to start. Michael can start a build when maintenance is completed if you let him know.<br />
* There is a rough priority hierachy of builds where master and stable branch release builds have priority. Avoiding builds during release periods if possible is helpful.<br />
* Being present on #yp-infra on IRC is helpful and infrastructure/autobuilder discussion may happen there<br />
* If a partially complete build is no longer useful for some reason, please stop it to allow the resources to be used by others<br />
<br />
=== Resources ===<br />
<br />
* [[Accessing Autobuilders]]<br />
* [https://autobuilder.yocto.io/pub/non-release/ non-release build output] -- https://autobuilder.yocto.io/pub/non-release/<br />
* [https://autobuilder.yocto.io/pub/releases/ release build output] -- https://autobuilder.yocto.io/pub/releases/<br />
* [[AutoBuilder Maintenance]]<br />
* [[AutoBuilder Cluster Setup]]<br />
* [[Frequently Asked Yocto Autobuilder Questions]]<br />
* [[Entropy on Autobuilders]]</div>BillMillshttps://wiki.yoctoproject.org/wiki/index.php?title=The_Yocto_Autobuilder&diff=85916The Yocto Autobuilder2023-09-07T18:12:30Z<p>BillMills: Fix releases upload URL in text. Link in the section below was already correct</p>
<hr />
<div>== The Yocto AutoBuilder ==<br />
<br />
The autobuilder '''[https://autobuilder.yoctoproject.org/typhoon/#/console Main Console]'''.<br />
<br />
The Yocto AutoBuilder is a buildbot (currently 3.x) based autobuilder implementation that can be used to build out and test custom distros utilizing OE-Core (either bare or through the poky repository)<br />
<br />
The source code can be downloaded from the '''[http://git.yoctoproject.org/cgit/cgit.cgi/yocto-autobuilder2/ yocto-autobuilder2]''' and '''[http://git.yoctoproject.org/cgit/cgit.cgi/yocto-autobuilder-helper/ yocto-autobuilder-helper]''' repositories.<br />
<br />
For details on the design and configuration of the AutoBuilder, refer to the documentation in those repositories.<br />
<br />
The yocto-autobuilder maintainer is [[User:Rpurdie | Richard Purdie]] (RP on IRC). All patches to the yocto-autobuilder2 should be sent to yocto@yoctoproject.org with "[yocto-autobuilder2]" in the Subject line. Please CC: richard.purdie@linuxfoundation.org. The hardware is maintained by the Linux Foundation on behalf of the Yocto Project and for infrastructure issues, please contact Michael Halstead (halstead on IRC).<br />
<br />
'''NOTE: please use autobuilder2''', autobuilder is dead [1], buildbot eight (aka 0.8.x) is dead.<br />
<br />
[1] http://git.yoctoproject.org/cgit.cgi/yocto-autobuilder/commit/?id=1369545f9819537535e4ab6ebeb49e7b173a8366<br />
<br />
=== Scheduled Builds ===<br />
<br />
The current active schedule can be seen in [https://git.yoctoproject.org/yocto-autobuilder2/tree/schedulers.py#n446 schedulers.py].<br />
<br />
The scheduled builds are:<br />
* a-quick on master every night on Monday to Saturday<br />
* a-full on master every Sunday night<br />
* metrics check each morning<br />
* check-layer for a number of meta-layers every night (master branch)<br />
* check-layer for a number of meta-layers one each night covering all active releases (spread over a week)<br />
* build performance checks 4 times a day on two distros<br />
* Auto Upgrade Helper twice a month<br />
* Doc rebuild on all branches for any commit that changes docs<br />
<br />
=== Starting Builds ===<br />
<br />
For autobuilder access, contact Michael Halstead <michael@yoctoproject.org> as an account is needed to start builds. These are usually available to stable branch maintainers or in special cases other layer maintainers for running builds on the project infrastructure. <br />
<br />
To start builds, from the main console you'd usually select 'a-quick' or 'a-full' from the top list of builders. If not logged in, login using the link on the top right of the page. You should then see a button "Start a-full build" or "Start a-quick build" which you can press. This opens a fairly complex form but in most cases you can use the "Release Shortcut Selector" to pre-populate the form with a given release's defaults. For a stable branch build on a test branch, you may then want to change the poky repository to point to poky-contrib and the branch to be the one you want to test. You should enter a reason for the build in the box at the top of the form. This is added to the [[BuildLog]] and us used by SWAT to decide what to do with bugs. When the form is correct, click "Start Build" at the bottom of the form.<br />
<br />
If making a release build, be sure to check all three check boxes, "Do we want to save build output?", "Generate a release?" and "Send QA alert emails?". The release milestone, release number and release rc number need to be filled in as appropriate too.<br />
<br />
The autobuilder can run multiple builds in parallel so builds can be queued as needed but please be sensible. The autobuilder users are usually around in #yp-infra on IRC which can be useful to schedule builds between us.<br />
<br />
The autobuilder maintenance window is morning for US PST on Fridays and builds should not be run over this period to allow weekly maintanance on the worker distros to be carried out.<br />
<br />
Autobuilder output for non-release builds is available at: https://autobuilder.yocto.io/pub/non-releases/ and for release builds: https://autobuilder.yocto.io/pub/release/.<br />
<br />
=== Autobuilder Build User Guidelines/Conditions of Use ===<br />
<br />
If you have the ability to run autobuilder builds there are some things you need to be mindful of:<br />
<br />
* It is expected that normally users should have resolved minor issues and done some testing before using the project infrastructure.<br />
* You are expected to triage the results of your own build<br />
* If you see unexplained failures, it is expected that bugs are filed for these, or where there are existing bugs, the bug should be updated. Please include which host/worker the build failed on. This allows triage to know which issues are occurring, their frequency and patterns like which host(s) they occur on.<br />
* The maintenance window is on Friday mornings US pacific time. Please do not start builds until maintenance is complete or run builds which wouldn't finish before maintenance is due to start. Michael can start a build when maintenance is completed if you let him know.<br />
* There is a rough priority hierachy of builds where master and stable branch release builds have priority. Avoiding builds during release periods if possible is helpful.<br />
* Being present on #yp-infra on IRC is helpful and infrastructure/autobuilder discussion may happen there<br />
* If a partially complete build is no longer useful for some reason, please stop it to allow the resources to be used by others<br />
<br />
=== Resources ===<br />
<br />
* [[Accessing Autobuilders]]<br />
* [https://autobuilder.yocto.io/pub/non-release/ non-release build output] -- https://autobuilder.yocto.io/pub/non-release/<br />
* [https://autobuilder.yocto.io/pub/releases/ release build output] -- https://autobuilder.yocto.io/pub/releases/<br />
* [[AutoBuilder Maintenance]]<br />
* [[AutoBuilder Cluster Setup]]<br />
* [[Frequently Asked Yocto Autobuilder Questions]]<br />
* [[Entropy on Autobuilders]]</div>BillMillshttps://wiki.yoctoproject.org/wiki/index.php?title=The_Yocto_Autobuilder&diff=85915The Yocto Autobuilder2023-09-07T17:56:43Z<p>BillMills: Outline the scheduled builds & make Autobuild versions more clear based on their modern numbering.</p>
<hr />
<div>== The Yocto AutoBuilder ==<br />
<br />
The autobuilder '''[https://autobuilder.yoctoproject.org/typhoon/#/console Main Console]'''.<br />
<br />
The Yocto AutoBuilder is a buildbot (currently 3.x) based autobuilder implementation that can be used to build out and test custom distros utilizing OE-Core (either bare or through the poky repository)<br />
<br />
The source code can be downloaded from the '''[http://git.yoctoproject.org/cgit/cgit.cgi/yocto-autobuilder2/ yocto-autobuilder2]''' and '''[http://git.yoctoproject.org/cgit/cgit.cgi/yocto-autobuilder-helper/ yocto-autobuilder-helper]''' repositories.<br />
<br />
For details on the design and configuration of the AutoBuilder, refer to the documentation in those repositories.<br />
<br />
The yocto-autobuilder maintainer is [[User:Rpurdie | Richard Purdie]] (RP on IRC). All patches to the yocto-autobuilder2 should be sent to yocto@yoctoproject.org with "[yocto-autobuilder2]" in the Subject line. Please CC: richard.purdie@linuxfoundation.org. The hardware is maintained by the Linux Foundation on behalf of the Yocto Project and for infrastructure issues, please contact Michael Halstead (halstead on IRC).<br />
<br />
'''NOTE: please use autobuilder2''', autobuilder is dead [1], buildbot eight (aka 0.8.x) is dead.<br />
<br />
[1] http://git.yoctoproject.org/cgit.cgi/yocto-autobuilder/commit/?id=1369545f9819537535e4ab6ebeb49e7b173a8366<br />
<br />
=== Scheduled Builds ===<br />
<br />
The current active schedule can be seen in [https://git.yoctoproject.org/yocto-autobuilder2/tree/schedulers.py#n446 schedulers.py].<br />
<br />
The scheduled builds are:<br />
* a-quick on master every night on Monday to Saturday<br />
* a-full on master every Sunday night<br />
* metrics check each morning<br />
* check-layer for a number of meta-layers every night (master branch)<br />
* check-layer for a number of meta-layers one each night covering all active releases (spread over a week)<br />
* build performance checks 4 times a day on two distros<br />
* Auto Upgrade Helper twice a month<br />
* Doc rebuild on all branches for any commit that changes docs<br />
<br />
=== Starting Builds ===<br />
<br />
For autobuilder access, contact Michael Halstead <michael@yoctoproject.org> as an account is needed to start builds. These are usually available to stable branch maintainers or in special cases other layer maintainers for running builds on the project infrastructure. <br />
<br />
To start builds, from the main console you'd usually select 'a-quick' or 'a-full' from the top list of builders. If not logged in, login using the link on the top right of the page. You should then see a button "Start a-full build" or "Start a-quick build" which you can press. This opens a fairly complex form but in most cases you can use the "Release Shortcut Selector" to pre-populate the form with a given release's defaults. For a stable branch build on a test branch, you may then want to change the poky repository to point to poky-contrib and the branch to be the one you want to test. You should enter a reason for the build in the box at the top of the form. This is added to the [[BuildLog]] and us used by SWAT to decide what to do with bugs. When the form is correct, click "Start Build" at the bottom of the form.<br />
<br />
If making a release build, be sure to check all three check boxes, "Do we want to save build output?", "Generate a release?" and "Send QA alert emails?". The release milestone, release number and release rc number need to be filled in as appropriate too.<br />
<br />
The autobuilder can run multiple builds in parallel so builds can be queued as needed but please be sensible. The autobuilder users are usually around in #yp-infra on IRC which can be useful to schedule builds between us.<br />
<br />
The autobuilder maintenance window is morning for US PST on Fridays and builds should not be run over this period to allow weekly maintanance on the worker distros to be carried out.<br />
<br />
Autobuilder output for non-release builds is available at: https://autobuilder.yocto.io/pub/non-release/ and for release builds: https://autobuilder.yocto.io/pub/release/.<br />
<br />
=== Autobuilder Build User Guidelines/Conditions of Use ===<br />
<br />
If you have the ability to run autobuilder builds there are some things you need to be mindful of:<br />
<br />
* It is expected that normally users should have resolved minor issues and done some testing before using the project infrastructure.<br />
* You are expected to triage the results of your own build<br />
* If you see unexplained failures, it is expected that bugs are filed for these, or where there are existing bugs, the bug should be updated. Please include which host/worker the build failed on. This allows triage to know which issues are occurring, their frequency and patterns like which host(s) they occur on.<br />
* The maintenance window is on Friday mornings US pacific time. Please do not start builds until maintenance is complete or run builds which wouldn't finish before maintenance is due to start. Michael can start a build when maintenance is completed if you let him know.<br />
* There is a rough priority hierachy of builds where master and stable branch release builds have priority. Avoiding builds during release periods if possible is helpful.<br />
* Being present on #yp-infra on IRC is helpful and infrastructure/autobuilder discussion may happen there<br />
* If a partially complete build is no longer useful for some reason, please stop it to allow the resources to be used by others<br />
<br />
=== Resources ===<br />
<br />
* [[Accessing Autobuilders]]<br />
* [https://autobuilder.yocto.io/pub/non-release/ non-release build output] -- https://autobuilder.yocto.io/pub/non-release/<br />
* [https://autobuilder.yocto.io/pub/releases/ release build output] -- https://autobuilder.yocto.io/pub/releases/<br />
* [[AutoBuilder Maintenance]]<br />
* [[AutoBuilder Cluster Setup]]<br />
* [[Frequently Asked Yocto Autobuilder Questions]]<br />
* [[Entropy on Autobuilders]]</div>BillMillshttps://wiki.yoctoproject.org/wiki/index.php?title=Member_Technical_Contacts&diff=85822Member Technical Contacts2023-06-15T16:39:34Z<p>BillMills: Update Linaro contacts</p>
<hr />
<div>This page tracks the official technical contributors to the YP core from each of the Yocto Project's member organizations. Note that many organizations provide more resources than just one, particularly in terms of hardware or specific feature support, which is why the Yocto Project is a de facto standard for building Linux for embedded systems.<br />
<br />
Platinum Members<br />
* Amazon: Richard Elberger <elberger@amazon.com>, Megan Knight <megankn@amazon.com><br />
* Arm: Ross Burton <ross.burton@arm.com>, Akanksha Jain <akanksha.jain2@arm.com>, Ellie Stanford-Reed <ellie.stanford-reed@arm.com><br />
* BMW: Mario Goulart <mario.goulart@bmw.de>, Nisha Parrakat <nisha.m.parrakat@bmw.de><br />
* Cisco: Taras Kondratiuk <takondra@cisco.com><br />
* Comcast: Raj, Khem <Khem_Raj@comcast.com><br />
* Exein: Giovanni Alberto Falcione <giovanni@exein.io><br />
* Intel: apoorv sangal <apoorvsangal@gmail.com><br />
* Meta: DJ (Dharmesh Jani) <janidb@fb.com><br />
* Microsoft: Paul Eggleton <paul.eggleton@microsoft.com><br />
* Wind River: Robert Yang <liezhi.yang@windriver.com>; Saul Wold <Saul.Wold@windriver.com><br />
* AMD/Xilinx: Mark Hatle <mhatle@xilinx.com><br />
<br />
Gold Members<br />
* AGL: Jan-Simon Moeller <jsmoeller@linuxfoundation.org>, Walt Miner <wminer@linuxfoundation.org><br />
* Huawei: Davide Ricci <davide.ricci@huawei.com><br />
* Renesas: Mr. Takamitsu Honda <takamitsu.honda.pv@renesas.com><br />
* Siemens: Chris Larson <chris_larson@mentor.com>, Wade Farnsworth <wade_farnsworth@mentor.com><br />
* Texas Instruments: Praneeth Bajjuri <praneeth@ti.com><br />
<br />
Silver Members<br />
* Axis: Hakan Rick <hakan.rick@axis.com>, Peter Kjellerstedt <peter.kjellerstedt@axis.com><br />
* Bootlin: Alexandre Belloni <alexandre.belloni@bootlin.com><br />
* Dell: Michael Brown <michael.e.brown@dell.com><br />
* Founderiesio: Ricardo Salveti <ricardo@foundries.io><br />
* LG: Kyunglik Min <dp.min@lge.com><br />
* Linaro: Bill Mills <bill.mills@linaro.org>, Mikko Rapeli <mikko.rapeli@linaro.org><br />
* Lineo Solutions: Masahiro Miyake <miya@lineo.co.jp><br />
* Roku: Cameron Esfahani <cesfahani@roku.com><br />
* Smile: Yoann Congal <yoann.congal@smile.fr><br />
* MontaVista: Armin Kuster <akuster@mvista.com><br />
* NXP: Lauren Post <lauren.post@nxp.com>, Tom Hochstein <tom.hochstein@nxp.com><br />
* Savoir-faire Linux: Christophe Villemer <christophe.villemer@savoirfairelinux.com>, Eloi Bail <eloi.bail@saviorfairelinux.com>, Jerome Oufella <jerome.oufella@saviorfairelinux.com><br />
* ST: Christophe Priouzeau <christophe.priouzeau@foss.st.com><br />
<br />
Technical Partners<br />
* OpenEmbedded: Philip Balister <philip@balister.org><br />
<br />
'''Note''': a ''private'' mailing list exists with all individuals listed here, mainly to facilitate the communication and the organization of meetings. All technical discussions are encouraged to be made on the existing, open, project mailing lists. If you believe you need to be added to the private list, please reach out to the Yocto Project Community Manager.</div>BillMillshttps://wiki.yoctoproject.org/wiki/index.php?title=Planning&diff=85486Planning2022-10-04T16:05:17Z<p>BillMills: Add note that current practice does not update this page</p>
<hr />
<div>Planning for features and schedule is done as a community. Details on the schedule, features, and development and release process are below. <br />
<br />
=== Notes ===<br />
'''Releases after 3.1 are not recorded here.''' Maintenance releases, development milestones, and feature wish lists are recorded in the weekly meetings. You will need to look around a bit for the information you want.<br />
<br />
=== Project Status and Release Cycle ===<br />
* [[Yocto Project v3.1 Status]]<br />
* [[Yocto Project v2.8 Status]] (became v3.0 )<br />
* [[Yocto Project v2.7 Status]] <br />
* [[Yocto Project v2.6 Status]] <br />
* [[Yocto Project v2.5 Status]]<br />
* [[Yocto Project v2.4 Status]] <br />
* [[Yocto Project v2.3 Status]] <br />
* [[Yocto Project v2.2 Status]] <br />
* [[Yocto Project v2.1 Status]]<br />
* [[Yocto Project v1.9 Status]] <br />
* [[Yocto Project v1.8 Status]] <br />
* [[Yocto Project v1.7 Status]] <br />
* [[Yocto Project v1.6 Status]] <br />
* [[Yocto Project v1.5 Status]] <br />
* [[Yocto Project v1.4 Status]]<br />
* [[Yocto Project v1.3 Status]]<br />
* [[Yocto Project v1.2 Status]]<br />
* [[Yocto Project v1.1 Release Criteria]]<br />
* [[Yocto Project v1.0 Release Criteria]]<br />
* [[Yocto Project v. 1.0 Release Cycle]]<br />
* [[Yocto Project v1.0.1 Release Criteria]]<br />
* [[Yocto Project v1.0 Release Criteria]]<br />
<br />
=== Roadmaps and Schedules ===<br />
* [[Yocto 3.1 Schedule]]<br />
* [[Yocto 2.8 Schedule]] (became 3.0)<br />
* [[Yocto 2.7 Schedule]]<br />
* [[Yocto 2.6 Schedule]]<br />
* [[Yocto 2.5 Schedule]]<br />
* [[Yocto 2.4 Schedule]] <br />
* [[Yocto 2.3 Schedule]] <br />
* [[Yocto 2.2 Schedule]] <br />
* [[Yocto 2.1 Schedule]]<br />
* [[Yocto 1.9 Schedule]]<br />
* [[Yocto 1.8 Schedule]] <br />
* [[Yocto 1.7 Schedule]] <br />
* [[Yocto 1.6 Schedule]] <br />
* [[Yocto 1.5 Schedule]]<br />
* [[Yocto 1.4 Schedule]] <br />
* [[Yocto 1.3 Schedule]]<br />
* [[Yocto 1.2 Schedule]]<br />
* [[Yocto 1.1 Schedule]]<br />
* [[Yocto 1.0 Schedule]]<br />
* [[Yocto Project Roadmap]]<br />
* [[YoctoCalendar]]<br />
* Point Release Calendar[https://www.google.com/calendar/embed?src=3a0927ctps51u8rs2jv1uligdc%40group.calendar.google.com&ctz=America/Los_Angeles]<br />
<br />
=== Features ===<br />
* [[Yocto 3.1 Features]]<br />
* [[Yocto 2.8 Features]] (renamed 3.0)<br />
* [[Yocto 2.7 Features]] <br />
* [[Yocto 2.6 Features]]<br />
* [[Yocto 2.5 Features]]<br />
* [[Yocto 2.4 Features]] <br />
* [[Yocto 2.3 Features]] <br />
* [[Yocto Feature Summary]]<br />
* [[Yocto 2.2 Features]] <br />
* [[Yocto 2.1 Features]]<br />
* [[Yocto 1.9 Features]]<br />
* [[Yocto 1.8 Features]]<br />
* [[Yocto 1.7 Features]] <br />
* [[Yocto 1.6 Features]] <br />
* [[Yocto 1.5 Features]]<br />
* [[Yocto 1.4 Features]] <br />
* [[Yocto 1.3 Features]] <br />
* [[Yocto 1.2 Features]]<br />
* [[Yocto General Features]] - This page contains general features across all Yocto releases.<br />
* [[Yocto 1.1 Features]]<br />
* [[Yocto Features]] (from v1.0)<br />
<br />
=== Release Table ===<br />
* [[Releases]] -- This is a table of information about the releases of Yocto Project.<br />
<br />
=== Stable branch maintenance ===<br />
* [[Stable branch maintenance]] -- This describes maintenance plans and policies for all packages which have been released<br />
<br />
=== Yocto Kernel Policy ===<br />
* [[Linux Yocto]] -- This describes the kernel Policy for the Yocto Project<br />
<br />
=== Yocto Build Failure Swat Team ===<br />
* [[Yocto Build Failure Swat Team]] -- This describes the SWAT team and its rotation. Disbanded.<br />
<br />
=== Bug Status Dashboards ===<br />
<br />
Weekly - https://wiki.yoctoproject.org/charts/combo.html<br />
<br />
Daily - https://wiki.yoctoproject.org/charts/daily/combo.html<br />
<br />
=== Development Methodology ===<br />
* [[Development Methodology]] -- This describes what to expect from development effort, planning and execution<br />
<br />
=== QA Status ===<br />
* [[2.7 QA Status]] -- This is the most current QA test run Status for YP 2.7 in progress.<br />
* [[2.6 QA Status]] -- This is the most current QA test run Status for YP 2.6 in progress.<br />
* [[2.5 QA Status]] -- This is the most current QA test run Status for YP 2.5 in progress.</div>BillMillshttps://wiki.yoctoproject.org/wiki/index.php?title=Member_Technical_Contacts&diff=81712Member Technical Contacts2020-12-02T20:23:30Z<p>BillMills: fix the email address for Ed Doxat</p>
<hr />
<div>This page tracks the official technical contributors to the YP core from each of the Yocto Project's member organizations. Note that many organizations provide more resources than just one, particularly in terms of hardware or specific feature support, which is why the Yocto Project is a de facto standard for building Linux for embedded systems.<br />
<br />
Platinum Members<br />
* Arm: Ed Doxat Ed.Doxat@arm.com<br />
* Cisco: Victor Kamensky kamensky@cisco.com<br />
* Comcast: Raj, Khem <Khem_Raj@comcast.com><br />
* Facebook: DJ (Dharmesh Jani) janidb@fb.com<br />
* Intel: apoorv sangal apoorvsangal@gmail.com<br />
* Microsoft: Paul Eggleton paul.eggleton@microsoft.com<br />
* Texas Instruments: Denys Dmytriyenko <denys@ti.com><br />
* Xilinx: Mark Hatle mhatle@xilinx.com<br />
<br />
Gold Members<br />
* AGL: Jan-Simon Moeller jsmoeller@linuxfoundation.org<br />
* Juniper Networks: Stu Grossman stu.grossman@gmail.com<br />
* Mentor Graphics: Chris Larson <chris_larson@mentor.com><br />
* Renesas: Mr. Takamitsu Honda <takamitsu.honda.pv@renesas.com><br />
* Wind River: Robert Yang <liezhi.yang@windriver.com>; Saul Wold Saul.Wold@windriver.com<br />
<br />
Silver Members<br />
* AMD: Wade Farnsworth wade_farnsworth@mentor.com<br />
* Dell: Michael Brown michael.e.brown@dell.com<br />
* Enea: Catalin Doras catalin.doras@enea.com<br />
* Founderiesio: Ricardo Salveti ricardo@foundries.io<br />
* LG: Minjae Kim nate.kim@lge.com<br />
* Linaro: Nicolas Dechesne <nicolas.dechesne@linaro.org><br />
* Lineo Solutions: Masahiro Miyake miya@lineo.co.jp<br />
* MontaVista: Armin Kuster <akuster@mvista.com><br />
* NXP: Lauren Post lauren.post@nxp.com<br />
* ST: Christophe Priouzeau <christophe.priouzeau@st.com><br />
<br />
Technical Partners<br />
* OpenEmbedded: Philip Balister <philip@balister.org></div>BillMillshttps://wiki.yoctoproject.org/wiki/index.php?title=Main_Page&diff=1577Main Page2011-05-03T23:01:08Z<p>BillMills: Add a link back to non-wiki Main page</p>
<hr />
<div>== Welcome to the Yocto Project Wiki! ==<br />
* [[Planning and Governance]]<br />
* [[Community Guidelines]]<br />
* [[Processes and Activities]]<br />
* [[Projects]]<br />
* [[Yocto Interest Groups]]<br />
* [[FAQ]]<br />
* [[Contributors]]<br />
<br />
== Other resources ==<br />
* [http://yoctoproject.org Yocto Project Front Page]</div>BillMillshttps://wiki.yoctoproject.org/wiki/index.php?title=BSP_Interest_Group&diff=1576BSP Interest Group2011-05-03T22:50:45Z<p>BillMills: add hyperlink to mailing list</p>
<hr />
<div>Welcome to the Yocto Project's BSP Interest Group<br />
<br />
This group is intended to work toward standards, practices, tips, and advice on how to create a BSP that integrates well with Yocto and openembedded-core.<br />
<br />
Want to help out? Sign up for the [https://lists.yoctoproject.org/listinfo/yocto-bsp mailing list]</div>BillMillshttps://wiki.yoctoproject.org/wiki/index.php?title=BSP_Interest_Group&diff=1575BSP Interest Group2011-05-03T22:48:46Z<p>BillMills: initial version</p>
<hr />
<div>Welcome to the Yocto Project's BSP Interest Group<br />
<br />
This group is intended to work toward standards, practices, tips, and advice on how to create a BSP that integrates well with Yocto and openembedded-core.<br />
<br />
Want to help out? Sign up for the mailing list</div>BillMillshttps://wiki.yoctoproject.org/wiki/index.php?title=Yocto_Interest_Groups&diff=1574Yocto Interest Groups2011-05-03T22:45:17Z<p>BillMills: Add BSP group</p>
<hr />
<div>== Welcome to Yocto Project Interest Groups! ==<br />
<br />
These are Bird of a Feather groups that further a specific interest, related to the Yocto project.<br />
<br />
* [[Infrastructure/Administrative Interest Group]]<br />
* [[BSP Interest Group]]</div>BillMills