https://wiki.yoctoproject.org/wiki/api.php?action=feedcontributions&user=Sgarman&feedformat=atomYocto Project - User contributions [en]2024-03-28T16:33:00ZUser contributionsMediaWiki 1.39.5https://wiki.yoctoproject.org/wiki/index.php?title=BSPs/FRI2&diff=8791BSPs/FRI22013-02-12T17:33:12Z<p>Sgarman: </p>
<hr />
<div>__TOC__<br />
<br />
== Resources ==<br />
[http://git.yoctoproject.org/cgit/cgit.cgi/meta-intel/tree/meta-fri2/README?h=master Latest FRI2 README]<br />
<br />
== Tips ==<br />
Use this space to share tips about using the FRI2. If you didn't find it in the README and it took you longer than 5 minutes to figure it out, consider placing it here and we can work it into the README as appropriate.<br />
<br />
=== Unable to view HDMI output on your monitor ===<br />
<br />
Some HDMI monitors do not appear to work with the HDMI output from the FRI2. Which displays work and which do not can be unpredictable; it may even be the case that individual monitors of the same make and model may work while others may not.<br />
<br />
As a workaround you can connect the FRI2 to the DVI connection on your monitor using an HDMI to DVI adapter.<br />
<br />
=== Obtaining the ti_3410.fw file needed by ti_usb_3410_5052 ===<br />
<br />
Debian (and perhaps other Linux distros) do not package ti_3410.fw (no, not even in lfirmware-linux-nonfree). The following bash script will use git to obtain just the one file from kernel.org and move it to where "modprobe ti_usb_3410_5052" will find it:<br />
<br />
#!/bin/bash<br />
sudo apt-get install git<br />
git clone -n git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git --depth 1<br />
cd linux-firmware<br />
git checkout HEAD ti_3410.fw<br />
sudo cp -p ti_3410.fw /lib/firmware<br />
<br />
The script is tested on Debian with 3.1.0 kernel and will need to be modified if your system uses RPM and/or does not follow the standard filesystem hierarchy.<br />
<br />
Note that <b>Ubuntu and Fedora both package it</b> with the linux-firmware package and Ubuntu also includes it in the various linux-image packages.<br />
<br />
== Known Issues ==<br />
=== Warning at arch/x86/kernel/apic/ipi.c ===<br />
WARNING: at [...] linux-yocto-3.2.18+git1+5b4c9dc78b5ae607173cc3ddab9bce1b5f78129b_1+76dc683eccc46804729a76b9d2fd425ba540a483-r1/linux/arch/x86/kernel/apic/ipi.c:109 default_send_IPI_mask_logical+0xa4/0xe0()<br />
Hardware name: Fish River Island II<br />
empty IPI mask<br />
Modules linked in:<br />
Pid: 1, comm: swapper/0 Not tainted 3.2.18-yocto-standard #1<br />
Call Trace:<br />
[<c103b8d3>] warn_slowpath_common+0x73/0xa0<br />
[<c1018234>] ? default_send_IPI_mask_logical+0xa4/0xe0<br />
...<br />
<br />
This appears to be a known issue with how IPIs are handled within the generic SMP infrastructure. A fix is being discussed on [https://lkml.org/lkml/2012/2/19/11 LKML], but the warning appears to be benign.</div>Sgarmanhttps://wiki.yoctoproject.org/wiki/index.php?title=Yocto_Point-Release_Development_Workflow&diff=6398Yocto Point-Release Development Workflow2012-06-22T18:29:20Z<p>Sgarman: </p>
<hr />
<div>Yocto 1.2, "denzil" was released on April 30, 2012. Work is now happening in parallel for 1.3 as well as the 1.2.1 point-release. This page describes some of the workflow/guidelines of what will go into the 1.2.1 release.<br />
<br />
Scott Garman is the maintainer of the 1.2.1 release. His email is scott.a.garman@intel.com and he can be found on Freenode IRC as zenlinux in the #yocto, #poky, and #oe channels. <br />
<br />
== Git Branches ==<br />
<br />
Scott is maintaining two git branches, one based on oe-core, and one based on poky:<br />
<br />
http://git.openembedded.org/openembedded-core-contrib/log/?h=sgarman/denzil-next<br />
<br />
http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=sgarman/denzil-next<br />
<br />
== Focus and Scope ==<br />
<br />
The primary focus for getting patches into 1.2.1 is bugfixing, security updates, and making sure that recently released Ubuntu, Fedora, and OpenSUSE distros work with this release. All other kinds of patches (e.g, performance improvements) will have a very high bar to reach for them to be accepted (i.e, it will have to be very clear they pose little risk to introducing more bugs or stability issues). Anything that breaks APIs or compatibility is off the table.<br />
<br />
Please mention in your pull requests if you wish to have your commits included in the 1.2.1 release.<br />
<br />
The intention is to include bugfixes for these bugs in the eventual release of 1.2.1:<br />
<br />
https://bugzilla.yoctoproject.org/buglist.cgi?query_format=advanced&list_id=4572&bug_status=NEW&bug_status=ACCEPTED&bug_status=REOPENED&bug_status=NEEDINFO&bug_status=WaitForUpstream&bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&target_milestone=1.2.1<br />
<br />
This list is not set in stone and may change at any time.<br />
<br />
== Workflow ==<br />
<br />
Scott will monitor the oe-core, poky, and yocto mailing lists for commits that are relevant for the 1.2.1 release (again, mentioning in a pull request that you want the pull's contents in 1.2.1 makes things much easier for him). After the commits get merged into oe-core master and/or poky master, Scott will add these commits to an '''sgarman/denzil-next-testing''' branch to run some basic build tests on. If the build tests pass, Scott will merge the commits to the corresponding '''sgarman/denzil-next''' branch(es).<br />
<br />
Please be aware that sgarman/denzil-next and especially sgarman/denzil-next-testing can be rebased at any time.<br />
<br />
==== Tips for Future Maintainers ====<br />
<br />
This is a list of some things I found it helpful to do when preparing the 1.2.1 release that I recommend to future stable release maintainers:<br />
<br />
Use only one working area to manage your git trees.<br />
<br />
I started off by bouncing between my laptop and desktop system when merging commits, and this was a disaster - it was too difficult to keep track of which branches on which system were up to date vs. the remote git repos. After switching to one work area, I managed to get this under control.<br />
<br />
Likewise, keep a single text file or some other reminder system to track the state of your branches and commits to watch for.<br />
<br />
I had to regularly comb through the commits in oe-core and poky master to make sure I wasn't missing potentially important commits. I kept a text file with the shortlog of the last commit I had researched to help make sure I wasn't missing any commits or re-reviewing the same ones. This text file also kept track of commit titles that came in to the mailing lists that were intended for 1.2.1 that were not yet in master, as a reminder of what I could expect to merge soon. Finally, this text file included a Release Notes section for me to make notes of things I would need to eventually include in the final Release Notes for 1.2.1.<br />
<br />
== Testing ==<br />
<br />
Building our reference images (core-image-minimal and core-image-sato) for all five of our QEMU architectures is the most basic testing that needs to be done on an ongoing basis (ideally, nightly) with the sgarman/denzil-next branches. Additionally, the following use cases also need to be exercised on a regular basis (i.e, weekly):<br />
<br />
* non-GPLv3 builds<br />
* poky-tiny distro builds<br />
* ADT installer builds<br />
* meta-qt3<br />
<br />
== Schedule ==<br />
<br />
The goal is for a release candidate to be ready for 1.2.1 approximately 6-8 weeks after the release of 1.2.</div>Sgarmanhttps://wiki.yoctoproject.org/wiki/index.php?title=Yocto_Point-Release_Development_Workflow&diff=5933Yocto Point-Release Development Workflow2012-05-17T00:28:20Z<p>Sgarman: /* 1.2.1 Bugfixes, poky */</p>
<hr />
<div>Yocto 1.2, "denzil" was released on April 30, 2012. Work is now happening in parallel for 1.3 as well as the 1.2.1 point-release. This page describes some of the workflow/guidelines of what will go into the 1.2.1 release.<br />
<br />
Scott Garman is the maintainer of the 1.2.1 release. His email is scott.a.garman@intel.com and he can be found on Freenode IRC as zenlinux in the #yocto, #poky, and #oe channels. <br />
<br />
== Git Branches ==<br />
<br />
Scott is maintaining two git branches, one based on oe-core, and one based on poky:<br />
<br />
http://git.openembedded.org/openembedded-core-contrib/log/?h=sgarman/denzil-next<br />
<br />
http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=sgarman/denzil-next<br />
<br />
== Focus and Scope ==<br />
<br />
The primary focus for getting patches into 1.2.1 is bugfixing, security updates, and making sure that recently released Ubuntu, Fedora, and OpenSUSE distros work with this release. All other kinds of patches (e.g, performance improvements) will have a very high bar to reach for them to be accepted (i.e, it will have to be very clear they pose little risk to introducing more bugs or stability issues). Anything that breaks APIs or compatibility is off the table.<br />
<br />
Please mention in your pull requests if you wish to have your commits included in the 1.2.1 release.<br />
<br />
The intention is to include bugfixes for these bugs in the eventual release of 1.2.1:<br />
<br />
https://bugzilla.yoctoproject.org/buglist.cgi?query_format=advanced&list_id=4572&bug_status=NEW&bug_status=ACCEPTED&bug_status=REOPENED&bug_status=NEEDINFO&bug_status=WaitForUpstream&bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&target_milestone=1.2.1<br />
<br />
This list is not set in stone and may change at any time.<br />
<br />
== Workflow ==<br />
<br />
Scott will monitor the oe-core and poky/yocto mailing lists for commits that are relevant for the 1.2.1 release (again, mentioning in a pull request that you want the pull's contents in 1.2.1 makes things much easier for him). After the commits get merged into oe-core master and/or poky master, Scott will add these commits to an '''sgarman/denzil-next-testing''' branch to run some basic build tests on. If the build tests pass, Scott will merge the commits to the corresponding '''sgarman/denzil-next''' branch(es).<br />
<br />
Please be aware that sgarman/denzil-next and especially sgarman/denzil-next-testing can be rebased at any time.<br />
<br />
== Testing ==<br />
<br />
Building our reference images (core-image-minimal and core-image-sato) for all five of our QEMU architectures is the most basic testing that needs to be done on an ongoing basis (ideally, nightly) with the denzil-next branches. Additionally, the following use cases also need to be exercised on a regular basis (i.e, weekly):<br />
<br />
* non-GPLv3 builds<br />
* poky-tiny distro builds<br />
* ADT installer builds<br />
* meta-qt3<br />
<br />
== Schedule ==<br />
<br />
The goal is for a release candidate to be ready for 1.2.1 approximately 6-8 weeks after the release of 1.2.<br />
<br />
== 1.2.1 Bug Status Summary ==<br />
<br />
=== 1.2.1 Bugfixes, oe-core ===<br />
<br />
Note that all of these fixes are also applied to the [http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=sgarman/denzil-next poky-based sgarman/denzil-next branch].<br />
<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=1538 1538]: Resolved as WORKSFORME<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=1858 1858]: Fixed with [http://git.openembedded.org/openembedded-core-contrib/commit/?h=sgarman/denzil-next&id=b1c28667592e736115ab5e603a12c2723b939cf2 b1c28667592e736115ab5e603a12c2723b939cf2]<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=1906 1906]: Fix was included in 1.2<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2297 2297]: Fixed with [http://git.openembedded.org/openembedded-core-contrib/commit/?h=sgarman/denzil-next&id=d7bf94647f17c0382caad8af0bdda837b14b22dc d7bf94647f17c0382caad8af0bdda837b14b22dc]<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2344 2344]: Resolved as NOTABUG<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2352 2352]: Fixed with [http://git.openembedded.org/openembedded-core-contrib/commit/?h=sgarman/denzil-next&id=6e2235a4d769b16ebf68d6bbed56d8bcc0e0c83f 6e2235a4d769b16ebf68d6bbed56d8bcc0e0c83f]<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2355 2355]: Fixed with [http://git.openembedded.org/openembedded-core-contrib/commit/?h=sgarman/denzil-next&id=98cb2efe4e9f3092d531c9fc809406c3ef559725 98cb2efe4e9f3092d531c9fc809406c3ef559725]<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2356 2356]: Fixed with [http://git.openembedded.org/openembedded-core/commit/?id=80c431989eef64d2c34a9cddb7fb95b7b9768706 80c431989eef64d2c34a9cddb7fb95b7b9768706]<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2362 2362]: Fix was included in 1.2<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2368 2368]: Fixed with [http://git.openembedded.org/openembedded-core-contrib/commit/?h=sgarman/denzil-next&id=51a122a5593c62d7ffd07f860e54a2fb0327959c 51a122a5593c62d7ffd07f860e54a2fb0327959c]<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2385 2385]: Fixed with [http://git.openembedded.org/openembedded-core-contrib/commit/?h=sgarman/denzil-next&id=36634e16c0a0c80674bacf20f9841e3b042bd5fd 36634e16c0a0c80674bacf20f9841e3b042bd5fd]<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2411 2411]: Fixed with [http://git.openembedded.org/openembedded-core-contrib/commit/?h=sgarman/denzil-next&id=540cd9d42a4db562e5eca431cec89ac5a6a05cab 540cd9d42a4db562e5eca431cec89ac5a6a05cab]<br />
<br />
=== 1.2.1 Bugfixes, poky ===<br />
<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=1892 1892]: Fix was included in 1.2<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=1912 1912]: Fix was included in 1.2<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2173 2173]: Fix was an external web site, no code commits needed<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2219 2219]: Fixed with [http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=sgarman/denzil-next&id=43262f39cc6f493e33fadca0c67d8f421868e0ba 43262f39cc6f493e33fadca0c67d8f421868e0ba]<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2330 2330]: Fixed with [http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=sgarman/denzil-next&id=166ab724c5c427f5a15fa7c5324aef71895bdfc2 166ab724c5c427f5a15fa7c5324aef71895bdfc2]<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2334 2334]: Fix was included in 1.2<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2335 2335]: Fixed with [http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=sgarman/denzil-next&id=334256dd0dbb511fce0ba001c36b541c2e954b48 334256dd0dbb511fce0ba001c36b541c2e954b48]<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2337 2337]: Resolved as a duplicate<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2340 2340]: Fixed with [http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=sgarman/denzil-next&id=6def01264d59f2786005f3fcdf03f33f8fc5366d 6def01264d59f2786005f3fcdf03f33f8fc5366d]<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2344 2344]: Resolved as NOTABUG<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2366 2366]: Fixed with [http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=sgarman/denzil-next&id=5aa69ed4aaa617351f7277f922eb2b1b3f34aafc 5aa69ed4aaa617351f7277f922eb2b1b3f34aafc]<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2371 2371]: Fixed with [http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=sgarman/denzil-next&id=2fc4b06a68beb2fa1eb923894ddf452bb899c35b 2fc4b06a68beb2fa1eb923894ddf452bb899c35b]<br />
<br />
=== 1.2.1 Bugfixes, eclipse-plugin ===<br />
<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2372 2372]: Fixed with [http://git.yoctoproject.org/cgit.cgi/eclipse-poky/commit/?id=a504837940e7cd00b790d99cb4a777c10721bf14 a504837940e7cd00b790d99cb4a777c10721bf14]</div>Sgarmanhttps://wiki.yoctoproject.org/wiki/index.php?title=Yocto_Point-Release_Development_Workflow&diff=5927Yocto Point-Release Development Workflow2012-05-16T23:24:17Z<p>Sgarman: /* 1.2.1 Bugfixes, oe-core */</p>
<hr />
<div>Yocto 1.2, "denzil" was released on April 30, 2012. Work is now happening in parallel for 1.3 as well as the 1.2.1 point-release. This page describes some of the workflow/guidelines of what will go into the 1.2.1 release.<br />
<br />
Scott Garman is the maintainer of the 1.2.1 release. His email is scott.a.garman@intel.com and he can be found on Freenode IRC as zenlinux in the #yocto, #poky, and #oe channels. <br />
<br />
== Git Branches ==<br />
<br />
Scott is maintaining two git branches, one based on oe-core, and one based on poky:<br />
<br />
http://git.openembedded.org/openembedded-core-contrib/log/?h=sgarman/denzil-next<br />
<br />
http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=sgarman/denzil-next<br />
<br />
== Focus and Scope ==<br />
<br />
The primary focus for getting patches into 1.2.1 is bugfixing, security updates, and making sure that recently released Ubuntu, Fedora, and OpenSUSE distros work with this release. All other kinds of patches (e.g, performance improvements) will have a very high bar to reach for them to be accepted (i.e, it will have to be very clear they pose little risk to introducing more bugs or stability issues). Anything that breaks APIs or compatibility is off the table.<br />
<br />
Please mention in your pull requests if you wish to have your commits included in the 1.2.1 release.<br />
<br />
The intention is to include bugfixes for these bugs in the eventual release of 1.2.1:<br />
<br />
https://bugzilla.yoctoproject.org/buglist.cgi?query_format=advanced&list_id=4572&bug_status=NEW&bug_status=ACCEPTED&bug_status=REOPENED&bug_status=NEEDINFO&bug_status=WaitForUpstream&bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&target_milestone=1.2.1<br />
<br />
This list is not set in stone and may change at any time.<br />
<br />
== Workflow ==<br />
<br />
Scott will monitor the oe-core and poky/yocto mailing lists for commits that are relevant for the 1.2.1 release (again, mentioning in a pull request that you want the pull's contents in 1.2.1 makes things much easier for him). After the commits get merged into oe-core master and/or poky master, Scott will add these commits to an '''sgarman/denzil-next-testing''' branch to run some basic build tests on. If the build tests pass, Scott will merge the commits to the corresponding '''sgarman/denzil-next''' branch(es).<br />
<br />
Please be aware that sgarman/denzil-next and especially sgarman/denzil-next-testing can be rebased at any time.<br />
<br />
== Testing ==<br />
<br />
Building our reference images (core-image-minimal and core-image-sato) for all five of our QEMU architectures is the most basic testing that needs to be done on an ongoing basis (ideally, nightly) with the denzil-next branches. Additionally, the following use cases also need to be exercised on a regular basis (i.e, weekly):<br />
<br />
* non-GPLv3 builds<br />
* poky-tiny distro builds<br />
* ADT installer builds<br />
* meta-qt3<br />
<br />
== Schedule ==<br />
<br />
The goal is for a release candidate to be ready for 1.2.1 approximately 6-8 weeks after the release of 1.2.<br />
<br />
== 1.2.1 Bug Status Summary ==<br />
<br />
=== 1.2.1 Bugfixes, oe-core ===<br />
<br />
Note that all of these fixes are also applied to the [http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=sgarman/denzil-next poky-based sgarman/denzil-next branch].<br />
<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=1538 1538]: Resolved as WORKSFORME<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=1858 1858]: Fixed with [http://git.openembedded.org/openembedded-core-contrib/commit/?h=sgarman/denzil-next&id=b1c28667592e736115ab5e603a12c2723b939cf2 b1c28667592e736115ab5e603a12c2723b939cf2]<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=1906 1906]: Fix was included in 1.2<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2297 2297]: Fixed with [http://git.openembedded.org/openembedded-core-contrib/commit/?h=sgarman/denzil-next&id=d7bf94647f17c0382caad8af0bdda837b14b22dc d7bf94647f17c0382caad8af0bdda837b14b22dc]<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2344 2344]: Resolved as NOTABUG<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2352 2352]: Fixed with [http://git.openembedded.org/openembedded-core-contrib/commit/?h=sgarman/denzil-next&id=6e2235a4d769b16ebf68d6bbed56d8bcc0e0c83f 6e2235a4d769b16ebf68d6bbed56d8bcc0e0c83f]<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2355 2355]: Fixed with [http://git.openembedded.org/openembedded-core-contrib/commit/?h=sgarman/denzil-next&id=98cb2efe4e9f3092d531c9fc809406c3ef559725 98cb2efe4e9f3092d531c9fc809406c3ef559725]<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2356 2356]: Fixed with [http://git.openembedded.org/openembedded-core/commit/?id=80c431989eef64d2c34a9cddb7fb95b7b9768706 80c431989eef64d2c34a9cddb7fb95b7b9768706]<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2362 2362]: Fix was included in 1.2<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2368 2368]: Fixed with [http://git.openembedded.org/openembedded-core-contrib/commit/?h=sgarman/denzil-next&id=51a122a5593c62d7ffd07f860e54a2fb0327959c 51a122a5593c62d7ffd07f860e54a2fb0327959c]<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2385 2385]: Fixed with [http://git.openembedded.org/openembedded-core-contrib/commit/?h=sgarman/denzil-next&id=36634e16c0a0c80674bacf20f9841e3b042bd5fd 36634e16c0a0c80674bacf20f9841e3b042bd5fd]<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2411 2411]: Fixed with [http://git.openembedded.org/openembedded-core-contrib/commit/?h=sgarman/denzil-next&id=540cd9d42a4db562e5eca431cec89ac5a6a05cab 540cd9d42a4db562e5eca431cec89ac5a6a05cab]<br />
<br />
=== 1.2.1 Bugfixes, poky ===<br />
<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=1892 1892]: Fix was included in 1.2<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=1912 1912]: Fix was included in 1.2<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2173 2173]: Fix was an external web site, no code commits needed<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2219 2219]: Fixed with [http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=sgarman/denzil-next&id=43262f39cc6f493e33fadca0c67d8f421868e0ba 43262f39cc6f493e33fadca0c67d8f421868e0ba]<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2330 2330]: Fixed with [http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=sgarman/denzil-next&id=166ab724c5c427f5a15fa7c5324aef71895bdfc2 166ab724c5c427f5a15fa7c5324aef71895bdfc2]<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2334 2334]: TO BE INTEGRATED<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2335 2335]: Fixed with [http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=sgarman/denzil-next&id=334256dd0dbb511fce0ba001c36b541c2e954b48 334256dd0dbb511fce0ba001c36b541c2e954b48]<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2337 2337]: Resolved as a duplicate<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2340 2340]: Fixed with [http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=sgarman/denzil-next&id=6def01264d59f2786005f3fcdf03f33f8fc5366d 6def01264d59f2786005f3fcdf03f33f8fc5366d]<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2344 2344]: Resolved as NOTABUG<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2366 2366]: Fixed with [http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=sgarman/denzil-next&id=5aa69ed4aaa617351f7277f922eb2b1b3f34aafc 5aa69ed4aaa617351f7277f922eb2b1b3f34aafc]<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2371 2371]: Fixed with [http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=sgarman/denzil-next&id=2fc4b06a68beb2fa1eb923894ddf452bb899c35b 2fc4b06a68beb2fa1eb923894ddf452bb899c35b]<br />
<br />
=== 1.2.1 Bugfixes, eclipse-plugin ===<br />
<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2372 2372]: Fixed with [http://git.yoctoproject.org/cgit.cgi/eclipse-poky/commit/?id=a504837940e7cd00b790d99cb4a777c10721bf14 a504837940e7cd00b790d99cb4a777c10721bf14]</div>Sgarmanhttps://wiki.yoctoproject.org/wiki/index.php?title=Yocto_Point-Release_Development_Workflow&diff=5926Yocto Point-Release Development Workflow2012-05-16T23:17:52Z<p>Sgarman: /* 1.2.1 Bugfixes, oe-core */</p>
<hr />
<div>Yocto 1.2, "denzil" was released on April 30, 2012. Work is now happening in parallel for 1.3 as well as the 1.2.1 point-release. This page describes some of the workflow/guidelines of what will go into the 1.2.1 release.<br />
<br />
Scott Garman is the maintainer of the 1.2.1 release. His email is scott.a.garman@intel.com and he can be found on Freenode IRC as zenlinux in the #yocto, #poky, and #oe channels. <br />
<br />
== Git Branches ==<br />
<br />
Scott is maintaining two git branches, one based on oe-core, and one based on poky:<br />
<br />
http://git.openembedded.org/openembedded-core-contrib/log/?h=sgarman/denzil-next<br />
<br />
http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=sgarman/denzil-next<br />
<br />
== Focus and Scope ==<br />
<br />
The primary focus for getting patches into 1.2.1 is bugfixing, security updates, and making sure that recently released Ubuntu, Fedora, and OpenSUSE distros work with this release. All other kinds of patches (e.g, performance improvements) will have a very high bar to reach for them to be accepted (i.e, it will have to be very clear they pose little risk to introducing more bugs or stability issues). Anything that breaks APIs or compatibility is off the table.<br />
<br />
Please mention in your pull requests if you wish to have your commits included in the 1.2.1 release.<br />
<br />
The intention is to include bugfixes for these bugs in the eventual release of 1.2.1:<br />
<br />
https://bugzilla.yoctoproject.org/buglist.cgi?query_format=advanced&list_id=4572&bug_status=NEW&bug_status=ACCEPTED&bug_status=REOPENED&bug_status=NEEDINFO&bug_status=WaitForUpstream&bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&target_milestone=1.2.1<br />
<br />
This list is not set in stone and may change at any time.<br />
<br />
== Workflow ==<br />
<br />
Scott will monitor the oe-core and poky/yocto mailing lists for commits that are relevant for the 1.2.1 release (again, mentioning in a pull request that you want the pull's contents in 1.2.1 makes things much easier for him). After the commits get merged into oe-core master and/or poky master, Scott will add these commits to an '''sgarman/denzil-next-testing''' branch to run some basic build tests on. If the build tests pass, Scott will merge the commits to the corresponding '''sgarman/denzil-next''' branch(es).<br />
<br />
Please be aware that sgarman/denzil-next and especially sgarman/denzil-next-testing can be rebased at any time.<br />
<br />
== Testing ==<br />
<br />
Building our reference images (core-image-minimal and core-image-sato) for all five of our QEMU architectures is the most basic testing that needs to be done on an ongoing basis (ideally, nightly) with the denzil-next branches. Additionally, the following use cases also need to be exercised on a regular basis (i.e, weekly):<br />
<br />
* non-GPLv3 builds<br />
* poky-tiny distro builds<br />
* ADT installer builds<br />
* meta-qt3<br />
<br />
== Schedule ==<br />
<br />
The goal is for a release candidate to be ready for 1.2.1 approximately 6-8 weeks after the release of 1.2.<br />
<br />
== 1.2.1 Bug Status Summary ==<br />
<br />
=== 1.2.1 Bugfixes, oe-core ===<br />
<br />
Note that all of these fixes are also applied to the [http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=sgarman/denzil-next poky-based sgarman/denzil-next branch].<br />
<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=1538 1538]: Resolved as WORKSFORME<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=1858 1858]: Fixed with [http://git.openembedded.org/openembedded-core-contrib/commit/?h=sgarman/denzil-next&id=b1c28667592e736115ab5e603a12c2723b939cf2 b1c28667592e736115ab5e603a12c2723b939cf2]<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=1906 1906]: Fix was included in 1.2<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2297 2297]: Fixed with<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2344 2344]: Resolved as NOTABUG<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2352 2352]: Fixed with [http://git.openembedded.org/openembedded-core-contrib/commit/?h=sgarman/denzil-next&id=6e2235a4d769b16ebf68d6bbed56d8bcc0e0c83f 6e2235a4d769b16ebf68d6bbed56d8bcc0e0c83f]<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2355 2355]: Fixed with [http://git.openembedded.org/openembedded-core-contrib/commit/?h=sgarman/denzil-next&id=98cb2efe4e9f3092d531c9fc809406c3ef559725 98cb2efe4e9f3092d531c9fc809406c3ef559725]<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2356 2356]: Fixed with [http://git.openembedded.org/openembedded-core/commit/?id=80c431989eef64d2c34a9cddb7fb95b7b9768706 80c431989eef64d2c34a9cddb7fb95b7b9768706]<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2362 2362]: Fix was included in 1.2<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2368 2368]: Fixed with [http://git.openembedded.org/openembedded-core-contrib/commit/?h=sgarman/denzil-next&id=51a122a5593c62d7ffd07f860e54a2fb0327959c 51a122a5593c62d7ffd07f860e54a2fb0327959c]<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2385 2385]: Fixed with [http://git.openembedded.org/openembedded-core-contrib/commit/?h=sgarman/denzil-next&id=36634e16c0a0c80674bacf20f9841e3b042bd5fd 36634e16c0a0c80674bacf20f9841e3b042bd5fd]<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2411 2411]: Fixed with [http://git.openembedded.org/openembedded-core-contrib/commit/?h=sgarman/denzil-next&id=540cd9d42a4db562e5eca431cec89ac5a6a05cab 540cd9d42a4db562e5eca431cec89ac5a6a05cab]<br />
<br />
=== 1.2.1 Bugfixes, poky ===<br />
<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=1892 1892]: Fix was included in 1.2<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=1912 1912]: Fix was included in 1.2<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2173 2173]: Fix was an external web site, no code commits needed<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2219 2219]: Fixed with [http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=sgarman/denzil-next&id=43262f39cc6f493e33fadca0c67d8f421868e0ba 43262f39cc6f493e33fadca0c67d8f421868e0ba]<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2330 2330]: Fixed with [http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=sgarman/denzil-next&id=166ab724c5c427f5a15fa7c5324aef71895bdfc2 166ab724c5c427f5a15fa7c5324aef71895bdfc2]<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2334 2334]: TO BE INTEGRATED<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2335 2335]: Fixed with [http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=sgarman/denzil-next&id=334256dd0dbb511fce0ba001c36b541c2e954b48 334256dd0dbb511fce0ba001c36b541c2e954b48]<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2337 2337]: Resolved as a duplicate<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2340 2340]: Fixed with [http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=sgarman/denzil-next&id=6def01264d59f2786005f3fcdf03f33f8fc5366d 6def01264d59f2786005f3fcdf03f33f8fc5366d]<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2344 2344]: Resolved as NOTABUG<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2366 2366]: Fixed with [http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=sgarman/denzil-next&id=5aa69ed4aaa617351f7277f922eb2b1b3f34aafc 5aa69ed4aaa617351f7277f922eb2b1b3f34aafc]<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2371 2371]: Fixed with [http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=sgarman/denzil-next&id=2fc4b06a68beb2fa1eb923894ddf452bb899c35b 2fc4b06a68beb2fa1eb923894ddf452bb899c35b]<br />
<br />
=== 1.2.1 Bugfixes, eclipse-plugin ===<br />
<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2372 2372]: Fixed with [http://git.yoctoproject.org/cgit.cgi/eclipse-poky/commit/?id=a504837940e7cd00b790d99cb4a777c10721bf14 a504837940e7cd00b790d99cb4a777c10721bf14]</div>Sgarmanhttps://wiki.yoctoproject.org/wiki/index.php?title=Yocto_Point-Release_Development_Workflow&diff=5925Yocto Point-Release Development Workflow2012-05-16T23:16:27Z<p>Sgarman: /* 1.2.1 Bugfixes, oe-core */</p>
<hr />
<div>Yocto 1.2, "denzil" was released on April 30, 2012. Work is now happening in parallel for 1.3 as well as the 1.2.1 point-release. This page describes some of the workflow/guidelines of what will go into the 1.2.1 release.<br />
<br />
Scott Garman is the maintainer of the 1.2.1 release. His email is scott.a.garman@intel.com and he can be found on Freenode IRC as zenlinux in the #yocto, #poky, and #oe channels. <br />
<br />
== Git Branches ==<br />
<br />
Scott is maintaining two git branches, one based on oe-core, and one based on poky:<br />
<br />
http://git.openembedded.org/openembedded-core-contrib/log/?h=sgarman/denzil-next<br />
<br />
http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=sgarman/denzil-next<br />
<br />
== Focus and Scope ==<br />
<br />
The primary focus for getting patches into 1.2.1 is bugfixing, security updates, and making sure that recently released Ubuntu, Fedora, and OpenSUSE distros work with this release. All other kinds of patches (e.g, performance improvements) will have a very high bar to reach for them to be accepted (i.e, it will have to be very clear they pose little risk to introducing more bugs or stability issues). Anything that breaks APIs or compatibility is off the table.<br />
<br />
Please mention in your pull requests if you wish to have your commits included in the 1.2.1 release.<br />
<br />
The intention is to include bugfixes for these bugs in the eventual release of 1.2.1:<br />
<br />
https://bugzilla.yoctoproject.org/buglist.cgi?query_format=advanced&list_id=4572&bug_status=NEW&bug_status=ACCEPTED&bug_status=REOPENED&bug_status=NEEDINFO&bug_status=WaitForUpstream&bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&target_milestone=1.2.1<br />
<br />
This list is not set in stone and may change at any time.<br />
<br />
== Workflow ==<br />
<br />
Scott will monitor the oe-core and poky/yocto mailing lists for commits that are relevant for the 1.2.1 release (again, mentioning in a pull request that you want the pull's contents in 1.2.1 makes things much easier for him). After the commits get merged into oe-core master and/or poky master, Scott will add these commits to an '''sgarman/denzil-next-testing''' branch to run some basic build tests on. If the build tests pass, Scott will merge the commits to the corresponding '''sgarman/denzil-next''' branch(es).<br />
<br />
Please be aware that sgarman/denzil-next and especially sgarman/denzil-next-testing can be rebased at any time.<br />
<br />
== Testing ==<br />
<br />
Building our reference images (core-image-minimal and core-image-sato) for all five of our QEMU architectures is the most basic testing that needs to be done on an ongoing basis (ideally, nightly) with the denzil-next branches. Additionally, the following use cases also need to be exercised on a regular basis (i.e, weekly):<br />
<br />
* non-GPLv3 builds<br />
* poky-tiny distro builds<br />
* ADT installer builds<br />
* meta-qt3<br />
<br />
== Schedule ==<br />
<br />
The goal is for a release candidate to be ready for 1.2.1 approximately 6-8 weeks after the release of 1.2.<br />
<br />
== 1.2.1 Bug Status Summary ==<br />
<br />
=== 1.2.1 Bugfixes, oe-core ===<br />
<br />
Note that all of these fixes are also applied to the [http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=sgarman/denzil-next poky-based sgarman/denzil-next branch].<br />
<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=1538 1538]: Resolved as WORKSFORME<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=1858 1858]: Fixed with [http://git.openembedded.org/openembedded-core-contrib/commit/?h=sgarman/denzil-next&id=b1c28667592e736115ab5e603a12c2723b939cf2 b1c28667592e736115ab5e603a12c2723b939cf2]<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=1906 1906]: Fix was included in 1.2<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2344 2344]: Resolved as NOTABUG<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2352 2352]: Fixed with [http://git.openembedded.org/openembedded-core-contrib/commit/?h=sgarman/denzil-next&id=6e2235a4d769b16ebf68d6bbed56d8bcc0e0c83f 6e2235a4d769b16ebf68d6bbed56d8bcc0e0c83f]<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2355 2355]: Fixed with [http://git.openembedded.org/openembedded-core-contrib/commit/?h=sgarman/denzil-next&id=98cb2efe4e9f3092d531c9fc809406c3ef559725 98cb2efe4e9f3092d531c9fc809406c3ef559725]<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2356 2356]: Fixed with [http://git.openembedded.org/openembedded-core/commit/?id=80c431989eef64d2c34a9cddb7fb95b7b9768706 80c431989eef64d2c34a9cddb7fb95b7b9768706]<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2362 2362]: Fix was included in 1.2<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2368 2368]: Fixed with [http://git.openembedded.org/openembedded-core-contrib/commit/?h=sgarman/denzil-next&id=51a122a5593c62d7ffd07f860e54a2fb0327959c 51a122a5593c62d7ffd07f860e54a2fb0327959c]<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2385 2385]: Fixed with [http://git.openembedded.org/openembedded-core-contrib/commit/?h=sgarman/denzil-next&id=36634e16c0a0c80674bacf20f9841e3b042bd5fd 36634e16c0a0c80674bacf20f9841e3b042bd5fd]<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2411 2411]: Fixed with [http://git.openembedded.org/openembedded-core-contrib/commit/?h=sgarman/denzil-next&id=540cd9d42a4db562e5eca431cec89ac5a6a05cab 540cd9d42a4db562e5eca431cec89ac5a6a05cab]<br />
<br />
=== 1.2.1 Bugfixes, poky ===<br />
<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=1892 1892]: Fix was included in 1.2<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=1912 1912]: Fix was included in 1.2<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2173 2173]: Fix was an external web site, no code commits needed<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2219 2219]: Fixed with [http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=sgarman/denzil-next&id=43262f39cc6f493e33fadca0c67d8f421868e0ba 43262f39cc6f493e33fadca0c67d8f421868e0ba]<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2330 2330]: Fixed with [http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=sgarman/denzil-next&id=166ab724c5c427f5a15fa7c5324aef71895bdfc2 166ab724c5c427f5a15fa7c5324aef71895bdfc2]<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2334 2334]: TO BE INTEGRATED<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2335 2335]: Fixed with [http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=sgarman/denzil-next&id=334256dd0dbb511fce0ba001c36b541c2e954b48 334256dd0dbb511fce0ba001c36b541c2e954b48]<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2337 2337]: Resolved as a duplicate<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2340 2340]: Fixed with [http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=sgarman/denzil-next&id=6def01264d59f2786005f3fcdf03f33f8fc5366d 6def01264d59f2786005f3fcdf03f33f8fc5366d]<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2344 2344]: Resolved as NOTABUG<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2366 2366]: Fixed with [http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=sgarman/denzil-next&id=5aa69ed4aaa617351f7277f922eb2b1b3f34aafc 5aa69ed4aaa617351f7277f922eb2b1b3f34aafc]<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2371 2371]: Fixed with [http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=sgarman/denzil-next&id=2fc4b06a68beb2fa1eb923894ddf452bb899c35b 2fc4b06a68beb2fa1eb923894ddf452bb899c35b]<br />
<br />
=== 1.2.1 Bugfixes, eclipse-plugin ===<br />
<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2372 2372]: Fixed with [http://git.yoctoproject.org/cgit.cgi/eclipse-poky/commit/?id=a504837940e7cd00b790d99cb4a777c10721bf14 a504837940e7cd00b790d99cb4a777c10721bf14]</div>Sgarmanhttps://wiki.yoctoproject.org/wiki/index.php?title=Yocto_Point-Release_Development_Workflow&diff=5922Yocto Point-Release Development Workflow2012-05-16T23:09:52Z<p>Sgarman: /* 1.2.1 Bugfixes, poky */</p>
<hr />
<div>Yocto 1.2, "denzil" was released on April 30, 2012. Work is now happening in parallel for 1.3 as well as the 1.2.1 point-release. This page describes some of the workflow/guidelines of what will go into the 1.2.1 release.<br />
<br />
Scott Garman is the maintainer of the 1.2.1 release. His email is scott.a.garman@intel.com and he can be found on Freenode IRC as zenlinux in the #yocto, #poky, and #oe channels. <br />
<br />
== Git Branches ==<br />
<br />
Scott is maintaining two git branches, one based on oe-core, and one based on poky:<br />
<br />
http://git.openembedded.org/openembedded-core-contrib/log/?h=sgarman/denzil-next<br />
<br />
http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=sgarman/denzil-next<br />
<br />
== Focus and Scope ==<br />
<br />
The primary focus for getting patches into 1.2.1 is bugfixing, security updates, and making sure that recently released Ubuntu, Fedora, and OpenSUSE distros work with this release. All other kinds of patches (e.g, performance improvements) will have a very high bar to reach for them to be accepted (i.e, it will have to be very clear they pose little risk to introducing more bugs or stability issues). Anything that breaks APIs or compatibility is off the table.<br />
<br />
Please mention in your pull requests if you wish to have your commits included in the 1.2.1 release.<br />
<br />
The intention is to include bugfixes for these bugs in the eventual release of 1.2.1:<br />
<br />
https://bugzilla.yoctoproject.org/buglist.cgi?query_format=advanced&list_id=4572&bug_status=NEW&bug_status=ACCEPTED&bug_status=REOPENED&bug_status=NEEDINFO&bug_status=WaitForUpstream&bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&target_milestone=1.2.1<br />
<br />
This list is not set in stone and may change at any time.<br />
<br />
== Workflow ==<br />
<br />
Scott will monitor the oe-core and poky/yocto mailing lists for commits that are relevant for the 1.2.1 release (again, mentioning in a pull request that you want the pull's contents in 1.2.1 makes things much easier for him). After the commits get merged into oe-core master and/or poky master, Scott will add these commits to an '''sgarman/denzil-next-testing''' branch to run some basic build tests on. If the build tests pass, Scott will merge the commits to the corresponding '''sgarman/denzil-next''' branch(es).<br />
<br />
Please be aware that sgarman/denzil-next and especially sgarman/denzil-next-testing can be rebased at any time.<br />
<br />
== Testing ==<br />
<br />
Building our reference images (core-image-minimal and core-image-sato) for all five of our QEMU architectures is the most basic testing that needs to be done on an ongoing basis (ideally, nightly) with the denzil-next branches. Additionally, the following use cases also need to be exercised on a regular basis (i.e, weekly):<br />
<br />
* non-GPLv3 builds<br />
* poky-tiny distro builds<br />
* ADT installer builds<br />
* meta-qt3<br />
<br />
== Schedule ==<br />
<br />
The goal is for a release candidate to be ready for 1.2.1 approximately 6-8 weeks after the release of 1.2.<br />
<br />
== 1.2.1 Bug Status Summary ==<br />
<br />
=== 1.2.1 Bugfixes, oe-core ===<br />
<br />
Note that all of these fixes are also applied to the [http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=sgarman/denzil-next poky-based sgarman/denzil-next branch].<br />
<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=1538 1538]: Resolved as WORKSFORME<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=1858 1858]: Fixed with [http://git.openembedded.org/openembedded-core-contrib/commit/?h=sgarman/denzil-next&id=b1c28667592e736115ab5e603a12c2723b939cf2 b1c28667592e736115ab5e603a12c2723b939cf2]<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=1906 1906]: Fix was included in 1.2<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2344 2344]: Resolved as NOTABUG<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2352 2352]: Fixed with [http://git.openembedded.org/openembedded-core-contrib/commit/?h=sgarman/denzil-next&id=6e2235a4d769b16ebf68d6bbed56d8bcc0e0c83f 6e2235a4d769b16ebf68d6bbed56d8bcc0e0c83f]<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2355 2355]: Fixed with [http://git.openembedded.org/openembedded-core-contrib/commit/?h=sgarman/denzil-next&id=98cb2efe4e9f3092d531c9fc809406c3ef559725 98cb2efe4e9f3092d531c9fc809406c3ef559725]<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2356 2356]: Fixed with [http://git.openembedded.org/openembedded-core/commit/?id=80c431989eef64d2c34a9cddb7fb95b7b9768706 80c431989eef64d2c34a9cddb7fb95b7b9768706]<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2362 2362]: Fix was included in 1.2<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2368 2368]: Fixed with [http://git.openembedded.org/openembedded-core-contrib/commit/?h=sgarman/denzil-next&id=51a122a5593c62d7ffd07f860e54a2fb0327959c 51a122a5593c62d7ffd07f860e54a2fb0327959c]<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2411 2411]: Fixed with [http://git.openembedded.org/openembedded-core-contrib/commit/?h=sgarman/denzil-next&id=540cd9d42a4db562e5eca431cec89ac5a6a05cab 540cd9d42a4db562e5eca431cec89ac5a6a05cab]<br />
<br />
=== 1.2.1 Bugfixes, poky ===<br />
<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=1892 1892]: Fix was included in 1.2<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=1912 1912]: Fix was included in 1.2<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2173 2173]: Fix was an external web site, no code commits needed<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2219 2219]: Fixed with [http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=sgarman/denzil-next&id=43262f39cc6f493e33fadca0c67d8f421868e0ba 43262f39cc6f493e33fadca0c67d8f421868e0ba]<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2330 2330]: Fixed with [http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=sgarman/denzil-next&id=166ab724c5c427f5a15fa7c5324aef71895bdfc2 166ab724c5c427f5a15fa7c5324aef71895bdfc2]<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2334 2334]: TO BE INTEGRATED<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2335 2335]: Fixed with [http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=sgarman/denzil-next&id=334256dd0dbb511fce0ba001c36b541c2e954b48 334256dd0dbb511fce0ba001c36b541c2e954b48]<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2337 2337]: Resolved as a duplicate<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2340 2340]: Fixed with [http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=sgarman/denzil-next&id=6def01264d59f2786005f3fcdf03f33f8fc5366d 6def01264d59f2786005f3fcdf03f33f8fc5366d]<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2344 2344]: Resolved as NOTABUG<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2366 2366]: Fixed with [http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=sgarman/denzil-next&id=5aa69ed4aaa617351f7277f922eb2b1b3f34aafc 5aa69ed4aaa617351f7277f922eb2b1b3f34aafc]<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2371 2371]: Fixed with [http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=sgarman/denzil-next&id=2fc4b06a68beb2fa1eb923894ddf452bb899c35b 2fc4b06a68beb2fa1eb923894ddf452bb899c35b]<br />
<br />
=== 1.2.1 Bugfixes, eclipse-plugin ===<br />
<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2372 2372]: Fixed with [http://git.yoctoproject.org/cgit.cgi/eclipse-poky/commit/?id=a504837940e7cd00b790d99cb4a777c10721bf14 a504837940e7cd00b790d99cb4a777c10721bf14]</div>Sgarmanhttps://wiki.yoctoproject.org/wiki/index.php?title=Yocto_Point-Release_Development_Workflow&diff=5920Yocto Point-Release Development Workflow2012-05-16T23:08:05Z<p>Sgarman: /* 1.2.1 Bug Status Summary */</p>
<hr />
<div>Yocto 1.2, "denzil" was released on April 30, 2012. Work is now happening in parallel for 1.3 as well as the 1.2.1 point-release. This page describes some of the workflow/guidelines of what will go into the 1.2.1 release.<br />
<br />
Scott Garman is the maintainer of the 1.2.1 release. His email is scott.a.garman@intel.com and he can be found on Freenode IRC as zenlinux in the #yocto, #poky, and #oe channels. <br />
<br />
== Git Branches ==<br />
<br />
Scott is maintaining two git branches, one based on oe-core, and one based on poky:<br />
<br />
http://git.openembedded.org/openembedded-core-contrib/log/?h=sgarman/denzil-next<br />
<br />
http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=sgarman/denzil-next<br />
<br />
== Focus and Scope ==<br />
<br />
The primary focus for getting patches into 1.2.1 is bugfixing, security updates, and making sure that recently released Ubuntu, Fedora, and OpenSUSE distros work with this release. All other kinds of patches (e.g, performance improvements) will have a very high bar to reach for them to be accepted (i.e, it will have to be very clear they pose little risk to introducing more bugs or stability issues). Anything that breaks APIs or compatibility is off the table.<br />
<br />
Please mention in your pull requests if you wish to have your commits included in the 1.2.1 release.<br />
<br />
The intention is to include bugfixes for these bugs in the eventual release of 1.2.1:<br />
<br />
https://bugzilla.yoctoproject.org/buglist.cgi?query_format=advanced&list_id=4572&bug_status=NEW&bug_status=ACCEPTED&bug_status=REOPENED&bug_status=NEEDINFO&bug_status=WaitForUpstream&bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&target_milestone=1.2.1<br />
<br />
This list is not set in stone and may change at any time.<br />
<br />
== Workflow ==<br />
<br />
Scott will monitor the oe-core and poky/yocto mailing lists for commits that are relevant for the 1.2.1 release (again, mentioning in a pull request that you want the pull's contents in 1.2.1 makes things much easier for him). After the commits get merged into oe-core master and/or poky master, Scott will add these commits to an '''sgarman/denzil-next-testing''' branch to run some basic build tests on. If the build tests pass, Scott will merge the commits to the corresponding '''sgarman/denzil-next''' branch(es).<br />
<br />
Please be aware that sgarman/denzil-next and especially sgarman/denzil-next-testing can be rebased at any time.<br />
<br />
== Testing ==<br />
<br />
Building our reference images (core-image-minimal and core-image-sato) for all five of our QEMU architectures is the most basic testing that needs to be done on an ongoing basis (ideally, nightly) with the denzil-next branches. Additionally, the following use cases also need to be exercised on a regular basis (i.e, weekly):<br />
<br />
* non-GPLv3 builds<br />
* poky-tiny distro builds<br />
* ADT installer builds<br />
* meta-qt3<br />
<br />
== Schedule ==<br />
<br />
The goal is for a release candidate to be ready for 1.2.1 approximately 6-8 weeks after the release of 1.2.<br />
<br />
== 1.2.1 Bug Status Summary ==<br />
<br />
=== 1.2.1 Bugfixes, oe-core ===<br />
<br />
Note that all of these fixes are also applied to the [http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=sgarman/denzil-next poky-based sgarman/denzil-next branch].<br />
<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=1538 1538]: Resolved as WORKSFORME<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=1858 1858]: Fixed with [http://git.openembedded.org/openembedded-core-contrib/commit/?h=sgarman/denzil-next&id=b1c28667592e736115ab5e603a12c2723b939cf2 b1c28667592e736115ab5e603a12c2723b939cf2]<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=1906 1906]: Fix was included in 1.2<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2344 2344]: Resolved as NOTABUG<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2352 2352]: Fixed with [http://git.openembedded.org/openembedded-core-contrib/commit/?h=sgarman/denzil-next&id=6e2235a4d769b16ebf68d6bbed56d8bcc0e0c83f 6e2235a4d769b16ebf68d6bbed56d8bcc0e0c83f]<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2355 2355]: Fixed with [http://git.openembedded.org/openembedded-core-contrib/commit/?h=sgarman/denzil-next&id=98cb2efe4e9f3092d531c9fc809406c3ef559725 98cb2efe4e9f3092d531c9fc809406c3ef559725]<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2356 2356]: Fixed with [http://git.openembedded.org/openembedded-core/commit/?id=80c431989eef64d2c34a9cddb7fb95b7b9768706 80c431989eef64d2c34a9cddb7fb95b7b9768706]<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2362 2362]: Fix was included in 1.2<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2368 2368]: Fixed with [http://git.openembedded.org/openembedded-core-contrib/commit/?h=sgarman/denzil-next&id=51a122a5593c62d7ffd07f860e54a2fb0327959c 51a122a5593c62d7ffd07f860e54a2fb0327959c]<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2411 2411]: Fixed with [http://git.openembedded.org/openembedded-core-contrib/commit/?h=sgarman/denzil-next&id=540cd9d42a4db562e5eca431cec89ac5a6a05cab 540cd9d42a4db562e5eca431cec89ac5a6a05cab]<br />
<br />
=== 1.2.1 Bugfixes, poky ===<br />
<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=1892 1892]: Fix was included in 1.2<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=1912 1912]: Fix was included in 1.2<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2173 2173]: Fix was an external web site, no code commits needed<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2219 2219]: Fixed with [http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=sgarman/denzil-next&id=43262f39cc6f493e33fadca0c67d8f421868e0ba 43262f39cc6f493e33fadca0c67d8f421868e0ba]<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2330 2330]: Fixed with [http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=sgarman/denzil-next&id=166ab724c5c427f5a15fa7c5324aef71895bdfc2 166ab724c5c427f5a15fa7c5324aef71895bdfc2]<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2334 2334]: TO BE INTEGRATED<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2335 2335]: Fixed with [http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=sgarman/denzil-next&id=334256dd0dbb511fce0ba001c36b541c2e954b48 334256dd0dbb511fce0ba001c36b541c2e954b48]<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2337 2337]: Resolved as a duplicate<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2340 2340]: TO BE INTEGRATED<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2344 2344]: Resolved as NOTABUG<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2366 2366]: Fixed with [http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=sgarman/denzil-next&id=5aa69ed4aaa617351f7277f922eb2b1b3f34aafc 5aa69ed4aaa617351f7277f922eb2b1b3f34aafc]<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2371 2371]: Fixed with [http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=sgarman/denzil-next&id=2fc4b06a68beb2fa1eb923894ddf452bb899c35b 2fc4b06a68beb2fa1eb923894ddf452bb899c35b]<br />
<br />
=== 1.2.1 Bugfixes, eclipse-plugin ===<br />
<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2372 2372]: Fixed with [http://git.yoctoproject.org/cgit.cgi/eclipse-poky/commit/?id=a504837940e7cd00b790d99cb4a777c10721bf14 a504837940e7cd00b790d99cb4a777c10721bf14]</div>Sgarmanhttps://wiki.yoctoproject.org/wiki/index.php?title=Yocto_Point-Release_Development_Workflow&diff=5917Yocto Point-Release Development Workflow2012-05-16T22:59:00Z<p>Sgarman: /* 1.2.1 Bugfixes, oe-core */</p>
<hr />
<div>Yocto 1.2, "denzil" was released on April 30, 2012. Work is now happening in parallel for 1.3 as well as the 1.2.1 point-release. This page describes some of the workflow/guidelines of what will go into the 1.2.1 release.<br />
<br />
Scott Garman is the maintainer of the 1.2.1 release. His email is scott.a.garman@intel.com and he can be found on Freenode IRC as zenlinux in the #yocto, #poky, and #oe channels. <br />
<br />
== Git Branches ==<br />
<br />
Scott is maintaining two git branches, one based on oe-core, and one based on poky:<br />
<br />
http://git.openembedded.org/openembedded-core-contrib/log/?h=sgarman/denzil-next<br />
<br />
http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=sgarman/denzil-next<br />
<br />
== Focus and Scope ==<br />
<br />
The primary focus for getting patches into 1.2.1 is bugfixing, security updates, and making sure that recently released Ubuntu, Fedora, and OpenSUSE distros work with this release. All other kinds of patches (e.g, performance improvements) will have a very high bar to reach for them to be accepted (i.e, it will have to be very clear they pose little risk to introducing more bugs or stability issues). Anything that breaks APIs or compatibility is off the table.<br />
<br />
Please mention in your pull requests if you wish to have your commits included in the 1.2.1 release.<br />
<br />
The intention is to include bugfixes for these bugs in the eventual release of 1.2.1:<br />
<br />
https://bugzilla.yoctoproject.org/buglist.cgi?query_format=advanced&list_id=4572&bug_status=NEW&bug_status=ACCEPTED&bug_status=REOPENED&bug_status=NEEDINFO&bug_status=WaitForUpstream&bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&target_milestone=1.2.1<br />
<br />
This list is not set in stone and may change at any time.<br />
<br />
== Workflow ==<br />
<br />
Scott will monitor the oe-core and poky/yocto mailing lists for commits that are relevant for the 1.2.1 release (again, mentioning in a pull request that you want the pull's contents in 1.2.1 makes things much easier for him). After the commits get merged into oe-core master and/or poky master, Scott will add these commits to an '''sgarman/denzil-next-testing''' branch to run some basic build tests on. If the build tests pass, Scott will merge the commits to the corresponding '''sgarman/denzil-next''' branch(es).<br />
<br />
Please be aware that sgarman/denzil-next and especially sgarman/denzil-next-testing can be rebased at any time.<br />
<br />
== Testing ==<br />
<br />
Building our reference images (core-image-minimal and core-image-sato) for all five of our QEMU architectures is the most basic testing that needs to be done on an ongoing basis (ideally, nightly) with the denzil-next branches. Additionally, the following use cases also need to be exercised on a regular basis (i.e, weekly):<br />
<br />
* non-GPLv3 builds<br />
* poky-tiny distro builds<br />
* ADT installer builds<br />
* meta-qt3<br />
<br />
== Schedule ==<br />
<br />
The goal is for a release candidate to be ready for 1.2.1 approximately 6-8 weeks after the release of 1.2.<br />
<br />
== 1.2.1 Bug Status Summary ==<br />
<br />
=== 1.2.1 Bugfixes, oe-core ===<br />
<br />
Note that all of these fixes are also applied to the [http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=sgarman/denzil-next poky-based sgarman/denzil-next branch].<br />
<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=1538 1538]: Resolved as WORKSFORME<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=1858 1858]: Fixed with [http://git.openembedded.org/openembedded-core-contrib/commit/?h=sgarman/denzil-next&id=b1c28667592e736115ab5e603a12c2723b939cf2 b1c28667592e736115ab5e603a12c2723b939cf2]<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=1906 1906]: Fix was included in 1.2<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2344 2344]: Resolved as NOTABUG<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2352 2352]: Fixed with [http://git.openembedded.org/openembedded-core-contrib/commit/?h=sgarman/denzil-next&id=6e2235a4d769b16ebf68d6bbed56d8bcc0e0c83f 6e2235a4d769b16ebf68d6bbed56d8bcc0e0c83f]<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2355 2355]: Fixed with [http://git.openembedded.org/openembedded-core-contrib/commit/?h=sgarman/denzil-next&id=98cb2efe4e9f3092d531c9fc809406c3ef559725 98cb2efe4e9f3092d531c9fc809406c3ef559725]<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2356 2356]: Fixed with [http://git.openembedded.org/openembedded-core/commit/?id=80c431989eef64d2c34a9cddb7fb95b7b9768706 80c431989eef64d2c34a9cddb7fb95b7b9768706]<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2362 2362]: Fix was included in 1.2<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2368 2368]: Fixed with [http://git.openembedded.org/openembedded-core-contrib/commit/?h=sgarman/denzil-next&id=51a122a5593c62d7ffd07f860e54a2fb0327959c 51a122a5593c62d7ffd07f860e54a2fb0327959c]<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2411 2411]: Fixed with [http://git.openembedded.org/openembedded-core-contrib/commit/?h=sgarman/denzil-next&id=540cd9d42a4db562e5eca431cec89ac5a6a05cab 540cd9d42a4db562e5eca431cec89ac5a6a05cab]<br />
<br />
=== 1.2.1 Bugfixes, poky ===<br />
<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=1892 1892]: Fix was included in 1.2<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=1912 1912]: Fix was included in 1.2<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2173 2173]: Fix was an external web site, no code commits needed<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2219 2219]: Fixed with [http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=sgarman/denzil-next&id=43262f39cc6f493e33fadca0c67d8f421868e0ba 43262f39cc6f493e33fadca0c67d8f421868e0ba]<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2330 2330]: Fixed with [http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=sgarman/denzil-next&id=166ab724c5c427f5a15fa7c5324aef71895bdfc2 166ab724c5c427f5a15fa7c5324aef71895bdfc2]<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2334 2334] TO BE INTEGRATED<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2335 2335] TO BE INTEGRATED<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2337 2337]: Resolved as a duplicate<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2340 2340] TO BE INTEGRATED<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2344 2344] Resolved as NOTABUG<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2366 2366]: Fixed with [http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=sgarman/denzil-next&id=5aa69ed4aaa617351f7277f922eb2b1b3f34aafc 5aa69ed4aaa617351f7277f922eb2b1b3f34aafc]<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2371 2371]: Fixed with [http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=sgarman/denzil-next&id=2fc4b06a68beb2fa1eb923894ddf452bb899c35b 2fc4b06a68beb2fa1eb923894ddf452bb899c35b]<br />
<br />
=== 1.2.1 Bugfixes, eclipse-plugin ===<br />
<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2372 2372]: Fixed with [http://git.yoctoproject.org/cgit.cgi/eclipse-poky/commit/?id=a504837940e7cd00b790d99cb4a777c10721bf14 a504837940e7cd00b790d99cb4a777c10721bf14]</div>Sgarmanhttps://wiki.yoctoproject.org/wiki/index.php?title=Yocto_Point-Release_Development_Workflow&diff=5916Yocto Point-Release Development Workflow2012-05-16T22:58:43Z<p>Sgarman: /* 1.2.1 Bug Status Summary */</p>
<hr />
<div>Yocto 1.2, "denzil" was released on April 30, 2012. Work is now happening in parallel for 1.3 as well as the 1.2.1 point-release. This page describes some of the workflow/guidelines of what will go into the 1.2.1 release.<br />
<br />
Scott Garman is the maintainer of the 1.2.1 release. His email is scott.a.garman@intel.com and he can be found on Freenode IRC as zenlinux in the #yocto, #poky, and #oe channels. <br />
<br />
== Git Branches ==<br />
<br />
Scott is maintaining two git branches, one based on oe-core, and one based on poky:<br />
<br />
http://git.openembedded.org/openembedded-core-contrib/log/?h=sgarman/denzil-next<br />
<br />
http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=sgarman/denzil-next<br />
<br />
== Focus and Scope ==<br />
<br />
The primary focus for getting patches into 1.2.1 is bugfixing, security updates, and making sure that recently released Ubuntu, Fedora, and OpenSUSE distros work with this release. All other kinds of patches (e.g, performance improvements) will have a very high bar to reach for them to be accepted (i.e, it will have to be very clear they pose little risk to introducing more bugs or stability issues). Anything that breaks APIs or compatibility is off the table.<br />
<br />
Please mention in your pull requests if you wish to have your commits included in the 1.2.1 release.<br />
<br />
The intention is to include bugfixes for these bugs in the eventual release of 1.2.1:<br />
<br />
https://bugzilla.yoctoproject.org/buglist.cgi?query_format=advanced&list_id=4572&bug_status=NEW&bug_status=ACCEPTED&bug_status=REOPENED&bug_status=NEEDINFO&bug_status=WaitForUpstream&bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&target_milestone=1.2.1<br />
<br />
This list is not set in stone and may change at any time.<br />
<br />
== Workflow ==<br />
<br />
Scott will monitor the oe-core and poky/yocto mailing lists for commits that are relevant for the 1.2.1 release (again, mentioning in a pull request that you want the pull's contents in 1.2.1 makes things much easier for him). After the commits get merged into oe-core master and/or poky master, Scott will add these commits to an '''sgarman/denzil-next-testing''' branch to run some basic build tests on. If the build tests pass, Scott will merge the commits to the corresponding '''sgarman/denzil-next''' branch(es).<br />
<br />
Please be aware that sgarman/denzil-next and especially sgarman/denzil-next-testing can be rebased at any time.<br />
<br />
== Testing ==<br />
<br />
Building our reference images (core-image-minimal and core-image-sato) for all five of our QEMU architectures is the most basic testing that needs to be done on an ongoing basis (ideally, nightly) with the denzil-next branches. Additionally, the following use cases also need to be exercised on a regular basis (i.e, weekly):<br />
<br />
* non-GPLv3 builds<br />
* poky-tiny distro builds<br />
* ADT installer builds<br />
* meta-qt3<br />
<br />
== Schedule ==<br />
<br />
The goal is for a release candidate to be ready for 1.2.1 approximately 6-8 weeks after the release of 1.2.<br />
<br />
== 1.2.1 Bug Status Summary ==<br />
<br />
=== 1.2.1 Bugfixes, oe-core ===<br />
<br />
Note that all of these fixes are also applied to the [http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=sgarman/denzil-next poky-based sgarman/denzil-next branch].<br />
<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=1538 1538] Resolved as WORKSFORME<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=1858 1858]: Fixed with [http://git.openembedded.org/openembedded-core-contrib/commit/?h=sgarman/denzil-next&id=b1c28667592e736115ab5e603a12c2723b939cf2 b1c28667592e736115ab5e603a12c2723b939cf2]<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=1906 1906]: Fix was included in 1.2<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2344 2344]: Resolved as NOTABUG<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2352 2352]: Fixed with [http://git.openembedded.org/openembedded-core-contrib/commit/?h=sgarman/denzil-next&id=6e2235a4d769b16ebf68d6bbed56d8bcc0e0c83f 6e2235a4d769b16ebf68d6bbed56d8bcc0e0c83f]<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2355 2355] Fixed with [http://git.openembedded.org/openembedded-core-contrib/commit/?h=sgarman/denzil-next&id=98cb2efe4e9f3092d531c9fc809406c3ef559725 98cb2efe4e9f3092d531c9fc809406c3ef559725]<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2356 2356]: Fixed with [http://git.openembedded.org/openembedded-core/commit/?id=80c431989eef64d2c34a9cddb7fb95b7b9768706 80c431989eef64d2c34a9cddb7fb95b7b9768706]<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2362 2362]: Fix was included in 1.2<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2368 2368]: Fixed with [http://git.openembedded.org/openembedded-core-contrib/commit/?h=sgarman/denzil-next&id=51a122a5593c62d7ffd07f860e54a2fb0327959c 51a122a5593c62d7ffd07f860e54a2fb0327959c]<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2411 2411] Fixed with [http://git.openembedded.org/openembedded-core-contrib/commit/?h=sgarman/denzil-next&id=540cd9d42a4db562e5eca431cec89ac5a6a05cab 540cd9d42a4db562e5eca431cec89ac5a6a05cab]<br />
<br />
=== 1.2.1 Bugfixes, poky ===<br />
<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=1892 1892]: Fix was included in 1.2<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=1912 1912]: Fix was included in 1.2<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2173 2173]: Fix was an external web site, no code commits needed<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2219 2219]: Fixed with [http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=sgarman/denzil-next&id=43262f39cc6f493e33fadca0c67d8f421868e0ba 43262f39cc6f493e33fadca0c67d8f421868e0ba]<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2330 2330]: Fixed with [http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=sgarman/denzil-next&id=166ab724c5c427f5a15fa7c5324aef71895bdfc2 166ab724c5c427f5a15fa7c5324aef71895bdfc2]<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2334 2334] TO BE INTEGRATED<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2335 2335] TO BE INTEGRATED<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2337 2337]: Resolved as a duplicate<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2340 2340] TO BE INTEGRATED<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2344 2344] Resolved as NOTABUG<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2366 2366]: Fixed with [http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=sgarman/denzil-next&id=5aa69ed4aaa617351f7277f922eb2b1b3f34aafc 5aa69ed4aaa617351f7277f922eb2b1b3f34aafc]<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2371 2371]: Fixed with [http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=sgarman/denzil-next&id=2fc4b06a68beb2fa1eb923894ddf452bb899c35b 2fc4b06a68beb2fa1eb923894ddf452bb899c35b]<br />
<br />
=== 1.2.1 Bugfixes, eclipse-plugin ===<br />
<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2372 2372]: Fixed with [http://git.yoctoproject.org/cgit.cgi/eclipse-poky/commit/?id=a504837940e7cd00b790d99cb4a777c10721bf14 a504837940e7cd00b790d99cb4a777c10721bf14]</div>Sgarmanhttps://wiki.yoctoproject.org/wiki/index.php?title=Yocto_Point-Release_Development_Workflow&diff=5901Yocto Point-Release Development Workflow2012-05-16T17:15:13Z<p>Sgarman: /* 1.2.1 Bug Status Summary */</p>
<hr />
<div>Yocto 1.2, "denzil" was released on April 30, 2012. Work is now happening in parallel for 1.3 as well as the 1.2.1 point-release. This page describes some of the workflow/guidelines of what will go into the 1.2.1 release.<br />
<br />
Scott Garman is the maintainer of the 1.2.1 release. His email is scott.a.garman@intel.com and he can be found on Freenode IRC as zenlinux in the #yocto, #poky, and #oe channels. <br />
<br />
== Git Branches ==<br />
<br />
Scott is maintaining two git branches, one based on oe-core, and one based on poky:<br />
<br />
http://git.openembedded.org/openembedded-core-contrib/log/?h=sgarman/denzil-next<br />
<br />
http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=sgarman/denzil-next<br />
<br />
== Focus and Scope ==<br />
<br />
The primary focus for getting patches into 1.2.1 is bugfixing, security updates, and making sure that recently released Ubuntu, Fedora, and OpenSUSE distros work with this release. All other kinds of patches (e.g, performance improvements) will have a very high bar to reach for them to be accepted (i.e, it will have to be very clear they pose little risk to introducing more bugs or stability issues). Anything that breaks APIs or compatibility is off the table.<br />
<br />
Please mention in your pull requests if you wish to have your commits included in the 1.2.1 release.<br />
<br />
The intention is to include bugfixes for these bugs in the eventual release of 1.2.1:<br />
<br />
https://bugzilla.yoctoproject.org/buglist.cgi?query_format=advanced&list_id=4572&bug_status=NEW&bug_status=ACCEPTED&bug_status=REOPENED&bug_status=NEEDINFO&bug_status=WaitForUpstream&bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&target_milestone=1.2.1<br />
<br />
This list is not set in stone and may change at any time.<br />
<br />
== Workflow ==<br />
<br />
Scott will monitor the oe-core and poky/yocto mailing lists for commits that are relevant for the 1.2.1 release (again, mentioning in a pull request that you want the pull's contents in 1.2.1 makes things much easier for him). After the commits get merged into oe-core master and/or poky master, Scott will add these commits to an '''sgarman/denzil-next-testing''' branch to run some basic build tests on. If the build tests pass, Scott will merge the commits to the corresponding '''sgarman/denzil-next''' branch(es).<br />
<br />
Please be aware that sgarman/denzil-next and especially sgarman/denzil-next-testing can be rebased at any time.<br />
<br />
== Testing ==<br />
<br />
Building our reference images (core-image-minimal and core-image-sato) for all five of our QEMU architectures is the most basic testing that needs to be done on an ongoing basis (ideally, nightly) with the denzil-next branches. Additionally, the following use cases also need to be exercised on a regular basis (i.e, weekly):<br />
<br />
* non-GPLv3 builds<br />
* poky-tiny distro builds<br />
* ADT installer builds<br />
* meta-qt3<br />
<br />
== Schedule ==<br />
<br />
The goal is for a release candidate to be ready for 1.2.1 approximately 6-8 weeks after the release of 1.2.<br />
<br />
== 1.2.1 Bug Status Summary ==<br />
<br />
=== 1.2.1 Bugfixes, oe-core ===<br />
<br />
Note that all of these fixes are also applied to the [http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=sgarman/denzil-next poky-based sgarman/denzil-next branch].<br />
<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=1538 1538] Resolved as WORKSFORME<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=1858 1858]: Fixed with [http://git.openembedded.org/openembedded-core-contrib/commit/?h=sgarman/denzil-next&id=b1c28667592e736115ab5e603a12c2723b939cf2 b1c28667592e736115ab5e603a12c2723b939cf2]<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=1906 1906]: Fix was included in 1.2<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2344 2344]: Resolved as NOTABUG<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2352 2352]: Fixed with [http://git.openembedded.org/openembedded-core-contrib/commit/?h=sgarman/denzil-next&id=6e2235a4d769b16ebf68d6bbed56d8bcc0e0c83f 6e2235a4d769b16ebf68d6bbed56d8bcc0e0c83f]<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2355 2355] TO BE INTEGRATED<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2356 2356]: Fixed with [http://git.openembedded.org/openembedded-core/commit/?id=80c431989eef64d2c34a9cddb7fb95b7b9768706 80c431989eef64d2c34a9cddb7fb95b7b9768706]<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2362 2362]: Fix was included in 1.2<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2368 2368]: Fixed with [http://git.openembedded.org/openembedded-core-contrib/commit/?h=sgarman/denzil-next&id=51a122a5593c62d7ffd07f860e54a2fb0327959c 51a122a5593c62d7ffd07f860e54a2fb0327959c]<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2411 2411] TO BE INTEGRATED<br />
<br />
=== 1.2.1 Bugfixes, poky ===<br />
<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=1892 1892]: Fix was included in 1.2<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=1912 1912]: Fix was included in 1.2<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2173 2173]: Fix was an external web site, no code commits needed<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2219 2219]: Fixed with [http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=sgarman/denzil-next&id=43262f39cc6f493e33fadca0c67d8f421868e0ba 43262f39cc6f493e33fadca0c67d8f421868e0ba]<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2330 2330]: Fixed with [http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=sgarman/denzil-next&id=166ab724c5c427f5a15fa7c5324aef71895bdfc2 166ab724c5c427f5a15fa7c5324aef71895bdfc2]<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2334 2334] TO BE INTEGRATED<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2335 2335] TO BE INTEGRATED<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2337 2337]: Resolved as a duplicate<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2340 2340] TO BE INTEGRATED<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2344 2344] Resolved as NOTABUG<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2366 2366]: Fixed with [http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=sgarman/denzil-next&id=5aa69ed4aaa617351f7277f922eb2b1b3f34aafc 5aa69ed4aaa617351f7277f922eb2b1b3f34aafc]<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2371 2371]: Fixed with [http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=sgarman/denzil-next&id=2fc4b06a68beb2fa1eb923894ddf452bb899c35b 2fc4b06a68beb2fa1eb923894ddf452bb899c35b]<br />
<br />
=== 1.2.1 Bugfixes, eclipse-plugin ===<br />
<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2372 2372]: Fixed with [http://git.yoctoproject.org/cgit.cgi/eclipse-poky/commit/?id=a504837940e7cd00b790d99cb4a777c10721bf14 a504837940e7cd00b790d99cb4a777c10721bf14]</div>Sgarmanhttps://wiki.yoctoproject.org/wiki/index.php?title=Yocto_Point-Release_Development_Workflow&diff=5870Yocto Point-Release Development Workflow2012-05-11T03:26:20Z<p>Sgarman: /* 1.2.1 Bug Status Summary */</p>
<hr />
<div>Yocto 1.2, "denzil" was released on April 30, 2012. Work is now happening in parallel for 1.3 as well as the 1.2.1 point-release. This page describes some of the workflow/guidelines of what will go into the 1.2.1 release.<br />
<br />
Scott Garman is the maintainer of the 1.2.1 release. His email is scott.a.garman@intel.com and he can be found on Freenode IRC as zenlinux in the #yocto, #poky, and #oe channels. <br />
<br />
== Git Branches ==<br />
<br />
Scott is maintaining two git branches, one based on oe-core, and one based on poky:<br />
<br />
http://git.openembedded.org/openembedded-core-contrib/log/?h=sgarman/denzil-next<br />
<br />
http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=sgarman/denzil-next<br />
<br />
== Focus and Scope ==<br />
<br />
The primary focus for getting patches into 1.2.1 is bugfixing, security updates, and making sure that recently released Ubuntu, Fedora, and OpenSUSE distros work with this release. All other kinds of patches (e.g, performance improvements) will have a very high bar to reach for them to be accepted (i.e, it will have to be very clear they pose little risk to introducing more bugs or stability issues). Anything that breaks APIs or compatibility is off the table.<br />
<br />
Please mention in your pull requests if you wish to have your commits included in the 1.2.1 release.<br />
<br />
The intention is to include bugfixes for these bugs in the eventual release of 1.2.1:<br />
<br />
https://bugzilla.yoctoproject.org/buglist.cgi?query_format=advanced&list_id=4572&bug_status=NEW&bug_status=ACCEPTED&bug_status=REOPENED&bug_status=NEEDINFO&bug_status=WaitForUpstream&bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&target_milestone=1.2.1<br />
<br />
This list is not set in stone and may change at any time.<br />
<br />
== Workflow ==<br />
<br />
Scott will monitor the oe-core and poky/yocto mailing lists for commits that are relevant for the 1.2.1 release (again, mentioning in a pull request that you want the pull's contents in 1.2.1 makes things much easier for him). After the commits get merged into oe-core master and/or poky master, Scott will add these commits to an '''sgarman/denzil-next-testing''' branch to run some basic build tests on. If the build tests pass, Scott will merge the commits to the corresponding '''sgarman/denzil-next''' branch(es).<br />
<br />
Please be aware that sgarman/denzil-next and especially sgarman/denzil-next-testing can be rebased at any time.<br />
<br />
== Testing ==<br />
<br />
Building our reference images (core-image-minimal and core-image-sato) for all five of our QEMU architectures is the most basic testing that needs to be done on an ongoing basis (ideally, nightly) with the denzil-next branches. Additionally, the following use cases also need to be exercised on a regular basis (i.e, weekly):<br />
<br />
* non-GPLv3 builds<br />
* poky-tiny distro builds<br />
* ADT installer builds<br />
* meta-qt3<br />
<br />
== Schedule ==<br />
<br />
The goal is for a release candidate to be ready for 1.2.1 approximately 6-8 weeks after the release of 1.2.<br />
<br />
== 1.2.1 Bug Status Summary ==<br />
<br />
=== 1.2.1 Bugfixes, oe-core ===<br />
<br />
Note that all of these fixes are also applied to the [http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=sgarman/denzil-next poky-based sgarman/denzil-next branch].<br />
<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=1858 1858]: Fixed with [http://git.openembedded.org/openembedded-core-contrib/commit/?h=sgarman/denzil-next&id=b1c28667592e736115ab5e603a12c2723b939cf2 b1c28667592e736115ab5e603a12c2723b939cf2]<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=1906 1906]: Fix was included in 1.2<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2344 2344]: Resolved as NOTABUG<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2352 2352]: Fixed with [http://git.openembedded.org/openembedded-core-contrib/commit/?h=sgarman/denzil-next&id=6e2235a4d769b16ebf68d6bbed56d8bcc0e0c83f 6e2235a4d769b16ebf68d6bbed56d8bcc0e0c83f]<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2362 2362]: Fix was included in 1.2<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2368 2368]: Fixed with [http://git.openembedded.org/openembedded-core-contrib/commit/?h=sgarman/denzil-next&id=51a122a5593c62d7ffd07f860e54a2fb0327959c 51a122a5593c62d7ffd07f860e54a2fb0327959c]<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2356 2356]: Fixed with [http://git.openembedded.org/openembedded-core/commit/?id=80c431989eef64d2c34a9cddb7fb95b7b9768706 80c431989eef64d2c34a9cddb7fb95b7b9768706]<br />
<br />
=== 1.2.1 Bugfixes, poky ===<br />
<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=1892 1892]: Fix was included in 1.2<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=1912 1912]: Fix was included in 1.2<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2173 2173]: Fix was an external web site, no code commits needed<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2219 2219]: Fixed with [http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=sgarman/denzil-next&id=43262f39cc6f493e33fadca0c67d8f421868e0ba 43262f39cc6f493e33fadca0c67d8f421868e0ba]<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2330 2330]: Fixed with [http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=sgarman/denzil-next&id=166ab724c5c427f5a15fa7c5324aef71895bdfc2 166ab724c5c427f5a15fa7c5324aef71895bdfc2]<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2337 2337]: Resolved as a duplicate<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2366 2366]: Fixed with [http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=sgarman/denzil-next&id=5aa69ed4aaa617351f7277f922eb2b1b3f34aafc 5aa69ed4aaa617351f7277f922eb2b1b3f34aafc]<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2371 2371]: Fixed with [http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=sgarman/denzil-next&id=2fc4b06a68beb2fa1eb923894ddf452bb899c35b 2fc4b06a68beb2fa1eb923894ddf452bb899c35b]<br />
<br />
=== 1.2.1 Bugfixes, eclipse-plugin ===<br />
<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2372 2372]: Fixed with [http://git.yoctoproject.org/cgit.cgi/eclipse-poky/commit/?id=a504837940e7cd00b790d99cb4a777c10721bf14 a504837940e7cd00b790d99cb4a777c10721bf14]</div>Sgarmanhttps://wiki.yoctoproject.org/wiki/index.php?title=Yocto_Point-Release_Development_Workflow&diff=5869Yocto Point-Release Development Workflow2012-05-11T02:56:12Z<p>Sgarman: /* 1.2.1 Bug Status Summary */</p>
<hr />
<div>Yocto 1.2, "denzil" was released on April 30, 2012. Work is now happening in parallel for 1.3 as well as the 1.2.1 point-release. This page describes some of the workflow/guidelines of what will go into the 1.2.1 release.<br />
<br />
Scott Garman is the maintainer of the 1.2.1 release. His email is scott.a.garman@intel.com and he can be found on Freenode IRC as zenlinux in the #yocto, #poky, and #oe channels. <br />
<br />
== Git Branches ==<br />
<br />
Scott is maintaining two git branches, one based on oe-core, and one based on poky:<br />
<br />
http://git.openembedded.org/openembedded-core-contrib/log/?h=sgarman/denzil-next<br />
<br />
http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=sgarman/denzil-next<br />
<br />
== Focus and Scope ==<br />
<br />
The primary focus for getting patches into 1.2.1 is bugfixing, security updates, and making sure that recently released Ubuntu, Fedora, and OpenSUSE distros work with this release. All other kinds of patches (e.g, performance improvements) will have a very high bar to reach for them to be accepted (i.e, it will have to be very clear they pose little risk to introducing more bugs or stability issues). Anything that breaks APIs or compatibility is off the table.<br />
<br />
Please mention in your pull requests if you wish to have your commits included in the 1.2.1 release.<br />
<br />
The intention is to include bugfixes for these bugs in the eventual release of 1.2.1:<br />
<br />
https://bugzilla.yoctoproject.org/buglist.cgi?query_format=advanced&list_id=4572&bug_status=NEW&bug_status=ACCEPTED&bug_status=REOPENED&bug_status=NEEDINFO&bug_status=WaitForUpstream&bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&target_milestone=1.2.1<br />
<br />
This list is not set in stone and may change at any time.<br />
<br />
== Workflow ==<br />
<br />
Scott will monitor the oe-core and poky/yocto mailing lists for commits that are relevant for the 1.2.1 release (again, mentioning in a pull request that you want the pull's contents in 1.2.1 makes things much easier for him). After the commits get merged into oe-core master and/or poky master, Scott will add these commits to an '''sgarman/denzil-next-testing''' branch to run some basic build tests on. If the build tests pass, Scott will merge the commits to the corresponding '''sgarman/denzil-next''' branch(es).<br />
<br />
Please be aware that sgarman/denzil-next and especially sgarman/denzil-next-testing can be rebased at any time.<br />
<br />
== Testing ==<br />
<br />
Building our reference images (core-image-minimal and core-image-sato) for all five of our QEMU architectures is the most basic testing that needs to be done on an ongoing basis (ideally, nightly) with the denzil-next branches. Additionally, the following use cases also need to be exercised on a regular basis (i.e, weekly):<br />
<br />
* non-GPLv3 builds<br />
* poky-tiny distro builds<br />
* ADT installer builds<br />
* meta-qt3<br />
<br />
== Schedule ==<br />
<br />
The goal is for a release candidate to be ready for 1.2.1 approximately 6-8 weeks after the release of 1.2.<br />
<br />
== 1.2.1 Bug Status Summary ==<br />
<br />
=== 1.2.1 Bugfixes, oe-core ===<br />
<br />
Note that all of these fixes are also applied to the [http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=sgarman/denzil-next poky-based sgarman/denzil-next branch].<br />
<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=1858 1858]: Fixed with [http://git.openembedded.org/openembedded-core-contrib/commit/?h=sgarman/denzil-next&id=b1c28667592e736115ab5e603a12c2723b939cf2 b1c28667592e736115ab5e603a12c2723b939cf2]<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=1906 1906]: Fix was included in 1.2<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2344 2344]: Resolved as NOTABUG<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2352 2352]: Fixed with [http://git.openembedded.org/openembedded-core-contrib/commit/?h=sgarman/denzil-next&id=6e2235a4d769b16ebf68d6bbed56d8bcc0e0c83f 6e2235a4d769b16ebf68d6bbed56d8bcc0e0c83f]<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2362 2362]: Fix was included in 1.2<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2368 2368]: Fixed with [http://git.openembedded.org/openembedded-core-contrib/commit/?h=sgarman/denzil-next&id=51a122a5593c62d7ffd07f860e54a2fb0327959c 51a122a5593c62d7ffd07f860e54a2fb0327959c]<br />
<br />
=== 1.2.1 Bugfixes, poky ===<br />
<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=1892 1892]: Fix was included in 1.2<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=1912 1912]: Fix was included in 1.2<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2173 2173]: Fix was an external web site, no code commits needed<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2219 2219]: Fixed with [http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=sgarman/denzil-next&id=43262f39cc6f493e33fadca0c67d8f421868e0ba 43262f39cc6f493e33fadca0c67d8f421868e0ba]<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2330 2330]: Fixed with [http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=sgarman/denzil-next&id=166ab724c5c427f5a15fa7c5324aef71895bdfc2 166ab724c5c427f5a15fa7c5324aef71895bdfc2]<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2337 2337]: Resolved as a duplicate<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2366 2366]: Fixed with [http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=sgarman/denzil-next&id=5aa69ed4aaa617351f7277f922eb2b1b3f34aafc 5aa69ed4aaa617351f7277f922eb2b1b3f34aafc]<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2371 2371]: Fixed with [http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=sgarman/denzil-next&id=2fc4b06a68beb2fa1eb923894ddf452bb899c35b 2fc4b06a68beb2fa1eb923894ddf452bb899c35b]<br />
<br />
=== 1.2.1 Bugfixes, eclipse-plugin ===<br />
<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2372 2372]: Fixed with [http://git.yoctoproject.org/cgit.cgi/eclipse-poky/commit/?id=a504837940e7cd00b790d99cb4a777c10721bf14 a504837940e7cd00b790d99cb4a777c10721bf14]</div>Sgarmanhttps://wiki.yoctoproject.org/wiki/index.php?title=Yocto_Point-Release_Development_Workflow&diff=5865Yocto Point-Release Development Workflow2012-05-09T16:17:54Z<p>Sgarman: </p>
<hr />
<div>Yocto 1.2, "denzil" was released on April 30, 2012. Work is now happening in parallel for 1.3 as well as the 1.2.1 point-release. This page describes some of the workflow/guidelines of what will go into the 1.2.1 release.<br />
<br />
Scott Garman is the maintainer of the 1.2.1 release. His email is scott.a.garman@intel.com and he can be found on Freenode IRC as zenlinux in the #yocto, #poky, and #oe channels. <br />
<br />
== Git Branches ==<br />
<br />
Scott is maintaining two git branches, one based on oe-core, and one based on poky:<br />
<br />
http://git.openembedded.org/openembedded-core-contrib/log/?h=sgarman/denzil-next<br />
<br />
http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=sgarman/denzil-next<br />
<br />
== Focus and Scope ==<br />
<br />
The primary focus for getting patches into 1.2.1 is bugfixing, security updates, and making sure that recently released Ubuntu, Fedora, and OpenSUSE distros work with this release. All other kinds of patches (e.g, performance improvements) will have a very high bar to reach for them to be accepted (i.e, it will have to be very clear they pose little risk to introducing more bugs or stability issues). Anything that breaks APIs or compatibility is off the table.<br />
<br />
Please mention in your pull requests if you wish to have your commits included in the 1.2.1 release.<br />
<br />
The intention is to include bugfixes for these bugs in the eventual release of 1.2.1:<br />
<br />
https://bugzilla.yoctoproject.org/buglist.cgi?query_format=advanced&list_id=4572&bug_status=NEW&bug_status=ACCEPTED&bug_status=REOPENED&bug_status=NEEDINFO&bug_status=WaitForUpstream&bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&target_milestone=1.2.1<br />
<br />
This list is not set in stone and may change at any time.<br />
<br />
== Workflow ==<br />
<br />
Scott will monitor the oe-core and poky/yocto mailing lists for commits that are relevant for the 1.2.1 release (again, mentioning in a pull request that you want the pull's contents in 1.2.1 makes things much easier for him). After the commits get merged into oe-core master and/or poky master, Scott will add these commits to an '''sgarman/denzil-next-testing''' branch to run some basic build tests on. If the build tests pass, Scott will merge the commits to the corresponding '''sgarman/denzil-next''' branch(es).<br />
<br />
Please be aware that sgarman/denzil-next and especially sgarman/denzil-next-testing can be rebased at any time.<br />
<br />
== Testing ==<br />
<br />
Building our reference images (core-image-minimal and core-image-sato) for all five of our QEMU architectures is the most basic testing that needs to be done on an ongoing basis (ideally, nightly) with the denzil-next branches. Additionally, the following use cases also need to be exercised on a regular basis (i.e, weekly):<br />
<br />
* non-GPLv3 builds<br />
* poky-tiny distro builds<br />
* ADT installer builds<br />
* meta-qt3<br />
<br />
== Schedule ==<br />
<br />
The goal is for a release candidate to be ready for 1.2.1 approximately 6-8 weeks after the release of 1.2.<br />
<br />
== 1.2.1 Bug Status Summary ==<br />
<br />
=== 1.2.1 Bugfixes, oe-core ===<br />
<br />
Note that all of these fixes are also applied to the [http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=sgarman/denzil-next poky-based sgarman/denzil-next branch].<br />
<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=1858 1858]: Fixed with [http://git.openembedded.org/openembedded-core-contrib/commit/?h=sgarman/denzil-next&id=b1c28667592e736115ab5e603a12c2723b939cf2 b1c28667592e736115ab5e603a12c2723b939cf2]<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=1906 1906]: Fix was included in 1.2<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2344 2344]: Resolved as NOTABUG<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2352 2352]: Fixed with [http://git.openembedded.org/openembedded-core-contrib/commit/?h=sgarman/denzil-next&id=6e2235a4d769b16ebf68d6bbed56d8bcc0e0c83f 6e2235a4d769b16ebf68d6bbed56d8bcc0e0c83f]<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2362 2362]: Fix was included in 1.2<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2368 2368]: Fixed with [http://git.openembedded.org/openembedded-core-contrib/commit/?h=sgarman/denzil-next&id=51a122a5593c62d7ffd07f860e54a2fb0327959c 51a122a5593c62d7ffd07f860e54a2fb0327959c]<br />
<br />
=== 1.2.1 Bugfixes, poky ===<br />
<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=1892 1892]: Fix was included in 1.2<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=1912 1912]: Fix was included in 1.2<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2173 2173]: Fix was an external web site, no code commits needed<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2219 2219]: Fixed with [http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=sgarman/denzil-next&id=43262f39cc6f493e33fadca0c67d8f421868e0ba 43262f39cc6f493e33fadca0c67d8f421868e0ba]<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2330 2330]: Fixed with [http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=sgarman/denzil-next&id=166ab724c5c427f5a15fa7c5324aef71895bdfc2 166ab724c5c427f5a15fa7c5324aef71895bdfc2]<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2337 2337]: Resolved as a duplicate<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2366 2366]: Fixed with [http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=sgarman/denzil-next&id=5aa69ed4aaa617351f7277f922eb2b1b3f34aafc 5aa69ed4aaa617351f7277f922eb2b1b3f34aafc]<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2371 2371]: Fixed with [http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=sgarman/denzil-next&id=2fc4b06a68beb2fa1eb923894ddf452bb899c35b 2fc4b06a68beb2fa1eb923894ddf452bb899c35b]</div>Sgarmanhttps://wiki.yoctoproject.org/wiki/index.php?title=Yocto_Point-Release_Development_Workflow&diff=5826Yocto Point-Release Development Workflow2012-05-08T04:24:41Z<p>Sgarman: /* 1.2.1 Bug Status */</p>
<hr />
<div>Yocto 1.2, "denzil" was released on April 30, 2012. Work is now happening in parallel for 1.3 as well as the 1.2.1 point-release. This page describes some of the workflow/guidelines of what will go into the 1.2.1 release.<br />
<br />
Scott Garman is the maintainer of the 1.2.1 release. His email is scott.a.garman@intel.com and he can be found on Freenode IRC as zenlinux in the #yocto, #poky, and #oe channels. <br />
<br />
== Git Branches ==<br />
<br />
Scott is maintaining two git branches, one based on oe-core, and one based on poky:<br />
<br />
http://git.openembedded.org/openembedded-core-contrib/log/?h=sgarman/denzil-next<br />
<br />
http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=sgarman/denzil-next<br />
<br />
== Focus and Scope ==<br />
<br />
The primary focus for getting patches into 1.2.1 is bugfixing, security updates, and making sure that recently released Ubuntu, Fedora, and OpenSUSE distros work with this release. All other kinds of patches (e.g, performance improvements) will have a very high bar to reach for them to be accepted (i.e, it will have to be very clear they pose little risk to introducing more bugs or stability issues). Anything that breaks APIs or compatibility is off the table.<br />
<br />
Please mention in your pull requests if you wish to have your commits included in the 1.2.1 release.<br />
<br />
The intention is to include bugfixes for these bugs in the eventual release of 1.2.1:<br />
<br />
https://bugzilla.yoctoproject.org/buglist.cgi?query_format=advanced&list_id=4572&bug_status=NEW&bug_status=ACCEPTED&bug_status=REOPENED&bug_status=NEEDINFO&bug_status=WaitForUpstream&bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&target_milestone=1.2.1<br />
<br />
This list is not set in stone and may change at any time.<br />
<br />
== Workflow ==<br />
<br />
Scott will monitor the oe-core and poky/yocto mailing lists for commits that are relevant for the 1.2.1 release (again, mentioning in a pull request that you want the pull's contents in 1.2.1 makes things much easier for him). After the commits get merged into oe-core master and/or poky master, Scott will add these commits to an '''sgarman/denzil-next-testing''' branch to run some basic build tests on. If the build tests pass, Scott will merge the commits to the corresponding '''sgarman/denzil-next''' branch(es).<br />
<br />
Please be aware that sgarman/denzil-next and especially sgarman/denzil-next-testing can be rebased at any time.<br />
<br />
== Schedule ==<br />
<br />
The goal is for a release candidate to be ready for 1.2.1 approximately 6-8 weeks after the release of 1.2.<br />
<br />
== 1.2.1 Bug Status Summary ==<br />
<br />
=== 1.2.1 Bugfixes, oe-core ===<br />
<br />
Note that all of these fixes are also applied to the [http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=sgarman/denzil-next poky-based sgarman/denzil-next branch].<br />
<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=1858 1858]: Fixed with [http://git.openembedded.org/openembedded-core-contrib/commit/?h=sgarman/denzil-next&id=b1c28667592e736115ab5e603a12c2723b939cf2 b1c28667592e736115ab5e603a12c2723b939cf2]<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=1906 1906]: Fix was included in 1.2<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2344 2344]: Resolved as NOTABUG<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2352 2352]: Fixed with [http://git.openembedded.org/openembedded-core-contrib/commit/?h=sgarman/denzil-next&id=6e2235a4d769b16ebf68d6bbed56d8bcc0e0c83f 6e2235a4d769b16ebf68d6bbed56d8bcc0e0c83f]<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2362 2362]: Fix was included in 1.2<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2368 2368]: Fixed with [http://git.openembedded.org/openembedded-core-contrib/commit/?h=sgarman/denzil-next&id=51a122a5593c62d7ffd07f860e54a2fb0327959c 51a122a5593c62d7ffd07f860e54a2fb0327959c]<br />
<br />
=== 1.2.1 Bugfixes, poky ===<br />
<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=1892 1892]: Fix was included in 1.2<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=1912 1912]: Fix was included in 1.2<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2173 2173]: Fix was an external web site, no code commits needed<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2219 2219]: Fixed with [http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=sgarman/denzil-next&id=43262f39cc6f493e33fadca0c67d8f421868e0ba 43262f39cc6f493e33fadca0c67d8f421868e0ba]<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2330 2330]: Fixed with [http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=sgarman/denzil-next&id=166ab724c5c427f5a15fa7c5324aef71895bdfc2 166ab724c5c427f5a15fa7c5324aef71895bdfc2]<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2337 2337]: Resolved as a duplicate<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2366 2366]: Fixed with [http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=sgarman/denzil-next&id=5aa69ed4aaa617351f7277f922eb2b1b3f34aafc 5aa69ed4aaa617351f7277f922eb2b1b3f34aafc]<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2371 2371]: Fixed with [http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=sgarman/denzil-next&id=2fc4b06a68beb2fa1eb923894ddf452bb899c35b 2fc4b06a68beb2fa1eb923894ddf452bb899c35b]</div>Sgarmanhttps://wiki.yoctoproject.org/wiki/index.php?title=Yocto_Point-Release_Development_Workflow&diff=5825Yocto Point-Release Development Workflow2012-05-08T04:24:22Z<p>Sgarman: </p>
<hr />
<div>Yocto 1.2, "denzil" was released on April 30, 2012. Work is now happening in parallel for 1.3 as well as the 1.2.1 point-release. This page describes some of the workflow/guidelines of what will go into the 1.2.1 release.<br />
<br />
Scott Garman is the maintainer of the 1.2.1 release. His email is scott.a.garman@intel.com and he can be found on Freenode IRC as zenlinux in the #yocto, #poky, and #oe channels. <br />
<br />
== Git Branches ==<br />
<br />
Scott is maintaining two git branches, one based on oe-core, and one based on poky:<br />
<br />
http://git.openembedded.org/openembedded-core-contrib/log/?h=sgarman/denzil-next<br />
<br />
http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=sgarman/denzil-next<br />
<br />
== Focus and Scope ==<br />
<br />
The primary focus for getting patches into 1.2.1 is bugfixing, security updates, and making sure that recently released Ubuntu, Fedora, and OpenSUSE distros work with this release. All other kinds of patches (e.g, performance improvements) will have a very high bar to reach for them to be accepted (i.e, it will have to be very clear they pose little risk to introducing more bugs or stability issues). Anything that breaks APIs or compatibility is off the table.<br />
<br />
Please mention in your pull requests if you wish to have your commits included in the 1.2.1 release.<br />
<br />
The intention is to include bugfixes for these bugs in the eventual release of 1.2.1:<br />
<br />
https://bugzilla.yoctoproject.org/buglist.cgi?query_format=advanced&list_id=4572&bug_status=NEW&bug_status=ACCEPTED&bug_status=REOPENED&bug_status=NEEDINFO&bug_status=WaitForUpstream&bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&target_milestone=1.2.1<br />
<br />
This list is not set in stone and may change at any time.<br />
<br />
== Workflow ==<br />
<br />
Scott will monitor the oe-core and poky/yocto mailing lists for commits that are relevant for the 1.2.1 release (again, mentioning in a pull request that you want the pull's contents in 1.2.1 makes things much easier for him). After the commits get merged into oe-core master and/or poky master, Scott will add these commits to an '''sgarman/denzil-next-testing''' branch to run some basic build tests on. If the build tests pass, Scott will merge the commits to the corresponding '''sgarman/denzil-next''' branch(es).<br />
<br />
Please be aware that sgarman/denzil-next and especially sgarman/denzil-next-testing can be rebased at any time.<br />
<br />
== Schedule ==<br />
<br />
The goal is for a release candidate to be ready for 1.2.1 approximately 6-8 weeks after the release of 1.2.<br />
<br />
== 1.2.1 Bug Status ==<br />
<br />
=== 1.2.1 Bugfixes, oe-core ===<br />
<br />
Note that all of these fixes are also applied to the [http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=sgarman/denzil-next poky-based sgarman/denzil-next branch].<br />
<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=1858 1858]: Fixed with [http://git.openembedded.org/openembedded-core-contrib/commit/?h=sgarman/denzil-next&id=b1c28667592e736115ab5e603a12c2723b939cf2 b1c28667592e736115ab5e603a12c2723b939cf2]<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=1906 1906]: Fix was included in 1.2<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2344 2344]: Resolved as NOTABUG<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2352 2352]: Fixed with [http://git.openembedded.org/openembedded-core-contrib/commit/?h=sgarman/denzil-next&id=6e2235a4d769b16ebf68d6bbed56d8bcc0e0c83f 6e2235a4d769b16ebf68d6bbed56d8bcc0e0c83f]<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2362 2362]: Fix was included in 1.2<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2368 2368]: Fixed with [http://git.openembedded.org/openembedded-core-contrib/commit/?h=sgarman/denzil-next&id=51a122a5593c62d7ffd07f860e54a2fb0327959c 51a122a5593c62d7ffd07f860e54a2fb0327959c]<br />
<br />
=== 1.2.1 Bugfixes, poky ===<br />
<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=1892 1892]: Fix was included in 1.2<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=1912 1912]: Fix was included in 1.2<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2173 2173]: Fix was an external web site, no code commits needed<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2219 2219]: Fixed with [http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=sgarman/denzil-next&id=43262f39cc6f493e33fadca0c67d8f421868e0ba 43262f39cc6f493e33fadca0c67d8f421868e0ba]<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2330 2330]: Fixed with [http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=sgarman/denzil-next&id=166ab724c5c427f5a15fa7c5324aef71895bdfc2 166ab724c5c427f5a15fa7c5324aef71895bdfc2]<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2337 2337]: Resolved as a duplicate<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2366 2366]: Fixed with [http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=sgarman/denzil-next&id=5aa69ed4aaa617351f7277f922eb2b1b3f34aafc 5aa69ed4aaa617351f7277f922eb2b1b3f34aafc]<br />
* [https://bugzilla.yoctoproject.org/show_bug.cgi?id=2371 2371]: Fixed with [http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=sgarman/denzil-next&id=2fc4b06a68beb2fa1eb923894ddf452bb899c35b 2fc4b06a68beb2fa1eb923894ddf452bb899c35b]</div>Sgarmanhttps://wiki.yoctoproject.org/wiki/index.php?title=Yocto_Point-Release_Development_Workflow&diff=5824Yocto Point-Release Development Workflow2012-05-08T04:22:38Z<p>Sgarman: Created page with "Yocto 1.2, "denzil" was released on April 30, 2012. Work is now happening in parallel for 1.3 as well as the 1.2.1 point-release. This page describes some of the workflow/guideli..."</p>
<hr />
<div>Yocto 1.2, "denzil" was released on April 30, 2012. Work is now happening in parallel for 1.3 as well as the 1.2.1 point-release. This page describes some of the workflow/guidelines of what will go into the 1.2.1 release.<br />
<br />
Scott Garman is the maintainer of the 1.2.1 release. His email is scott.a.garman@intel.com and he can be found on Freenode IRC as zenlinux in the #yocto, #poky, and #oe channels. <br />
<br />
== Git Branches ==<br />
<br />
Scott is maintaining two git branches, one based on oe-core, and one based on poky:<br />
<br />
http://git.openembedded.org/openembedded-core-contrib/log/?h=sgarman/denzil-next<br />
<br />
http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=sgarman/denzil-next<br />
<br />
== Focus and Scope ==<br />
<br />
The primary focus for getting patches into 1.2.1 is bugfixing, security updates, and making sure that recently released Ubuntu, Fedora, and OpenSUSE distros work with this release. All other kinds of patches (e.g, performance improvements) will have a very high bar to reach for them to be accepted (i.e, it will have to be very clear they pose little risk to introducing more bugs or stability issues). Anything that breaks APIs or compatibility is off the table.<br />
<br />
Please mention in your pull requests if you wish to have your commits included in the 1.2.1 release.<br />
<br />
The intention is to include bugfixes for these bugs in the eventual release of 1.2.1:<br />
<br />
https://bugzilla.yoctoproject.org/buglist.cgi?query_format=advanced&list_id=4572&bug_status=NEW&bug_status=ACCEPTED&bug_status=REOPENED&bug_status=NEEDINFO&bug_status=WaitForUpstream&bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&target_milestone=1.2.1<br />
<br />
This list is not set in stone and may change at any time.<br />
<br />
== Workflow ==<br />
<br />
Scott will monitor the oe-core and poky/yocto mailing lists for commits that are relevant for the 1.2.1 release (again, mentioning in a pull request that you want the pull's contents in 1.2.1 makes things much easier for him). After the commits get merged into oe-core master and/or poky master, Scott will add these commits to an '''sgarman/denzil-next-testing''' branch to run some basic build tests on. If the build tests pass, Scott will merge the commits to the corresponding '''sgarman/denzil-next''' branch(es).<br />
<br />
Please be aware that sgarman/denzil-next and especially sgarman/denzil-next-testing can be rebased at any time.<br />
<br />
== Schedule ==<br />
<br />
The goal is for a release candidate to be ready for 1.2.1 approximately 6-8 weeks after the release of 1.2.</div>Sgarmanhttps://wiki.yoctoproject.org/wiki/index.php?title=Processes_and_Activities&diff=5823Processes and Activities2012-05-08T04:19:56Z<p>Sgarman: </p>
<hr />
<div>Welcome to the Processes and Activities Page!<br />
<br />
* [[Contribution Guidelines]]<br />
* [[Recipe & Patch Style Guide]]<br />
* [[Distro Tracking]]<br />
* [[Best Known Methods (BKMs) for Package Updating]]<br />
* [[Working Behind a Network Proxy]]<br />
* [[SDK Generator]]<br />
* [[QA]]<br />
* [[Kernel]]<br />
* [[Core]]<br />
* [[Bugzilla Configuration and Bug Tracking]]<br />
* [[Yocto Point-Release Development Workflow]]<br />
* [[Yocto Release Engineering]]<br />
* [[Performance]]<br />
* [[Security]]<br />
* [[PAM Integration]]<br />
* [[Program Management Plan]]<br />
* [[Enable sstate cache]]<br />
* [[Image Recipes]]<br />
* [[Community Statistics]]</div>Sgarmanhttps://wiki.yoctoproject.org/wiki/index.php?title=Training&diff=3908Training2011-11-03T20:37:18Z<p>Sgarman: </p>
<hr />
<div>This page collects training materials as contributed by the community.<br />
<br />
== Embedded Linux Conference 2011 ==<br />
Thank you to Free-Electrons.com for the sweet contribution of these videos!<br />
<br />
[http://free-electrons.com/blog/elc-2011-videos/ Link to the Free-Electrons.com web page]<br />
<br />
* [http://elinux.org/images/7/7c/Elc2011_zanussi_wold.odp Building Custom Embedded Images with Yocto (slides)]<br />
* [http://free-electrons.com/pub/video/2011/elc/elc-2011-zanussi-wold-custom-embedded-images-yocto-x450p.webm Building Custom Embedded Images with Yocto (450x800 video)]<br />
* [https://wiki.yoctoproject.org/wiki/images/2/22/Elc11-yocto-kernel-tutorial.pdf Yocto Project: Practical Kernel Development Tutorial (slides)]<br />
* [http://free-electrons.com/pub/video/2011/elc/elc-2011-hart-yocto-kernel-development-x450p.webm Yocto Project: Practical Kernel Development Tutorial (450x800 video)]<br />
* [http://elinux.org/images/e/e6/ELC_Yocto_ADT_2011_davest.odp The Yocto Project and its Application Development Toolkit (ADT) (slides)]<br />
* [http://free-electrons.com/pub/video/2011/elc/elc-2011-stewart-yocto-appdev-toolkit-x450p.webm The Yocto Project and its Application Development Toolkit (ADT) (450x800 video)]<br />
* [http://elinux.org/images/e/ec/Elc2011_flanagan.pdf Delivering Predictability: The Yocto Project Autobuilder, Automated Sanity Testing, License Collection, and Build Statistics Tracking (slides)]<br />
* [http://free-electrons.com/pub/video/2011/elc/elc-2011-flanagan-yocto-autobuilder-x450p.webm Delivering Predictability: The Yocto Project Autobuilder, Automated Sanity Testing, License Collection, and Build Statistics Tracking (450x800 video)]<br />
<br />
== Intel Developer Forum 2011 ==<br />
<br />
* [http://wiki.yoctoproject.org/wiki/images/7/74/IDF2011_SFTL003_YoctoProject.pdf Create a Custom Embedded Linux OS for Any Embedded Device Using the Yocto Project (hands-on lab, PDF slides, 2011-09)]<br />
<br />
== Miscellaneous ==<br />
<br />
* [http://wiki.yoctoproject.org/wiki/images/e/e6/Custom_Users_Groups_in_Yocto1.1.pdf Using Custom Users/Groups in Yocto 1.1 (PDF slides, 2011-08-10)]</div>Sgarmanhttps://wiki.yoctoproject.org/wiki/index.php?title=File:IDF2011_SFTL003_YoctoProject.pdf&diff=3907File:IDF2011 SFTL003 YoctoProject.pdf2011-11-03T20:35:40Z<p>Sgarman: Slides for the hands-on lab taught at the 2011 Intel Developer Forum conference in San Fransisco, CA.</p>
<hr />
<div>Slides for the hands-on lab taught at the 2011 Intel Developer Forum conference in San Fransisco, CA.</div>Sgarmanhttps://wiki.yoctoproject.org/wiki/index.php?title=Training&diff=3906Training2011-11-03T20:34:31Z<p>Sgarman: Added IDF hands-on lab presentation</p>
<hr />
<div>This page collects training materials as contributed by the community.<br />
<br />
== Embedded Linux Conference 2011 ==<br />
Thank you to Free-Electrons.com for the sweet contribution of these videos!<br />
<br />
[http://free-electrons.com/blog/elc-2011-videos/ Link to the Free-Electrons.com web page]<br />
<br />
* [http://elinux.org/images/7/7c/Elc2011_zanussi_wold.odp Building Custom Embedded Images with Yocto (slides)]<br />
* [http://free-electrons.com/pub/video/2011/elc/elc-2011-zanussi-wold-custom-embedded-images-yocto-x450p.webm Building Custom Embedded Images with Yocto (450x800 video)]<br />
* [https://wiki.yoctoproject.org/wiki/images/2/22/Elc11-yocto-kernel-tutorial.pdf Yocto Project: Practical Kernel Development Tutorial (slides)]<br />
* [http://free-electrons.com/pub/video/2011/elc/elc-2011-hart-yocto-kernel-development-x450p.webm Yocto Project: Practical Kernel Development Tutorial (450x800 video)]<br />
* [http://elinux.org/images/e/e6/ELC_Yocto_ADT_2011_davest.odp The Yocto Project and its Application Development Toolkit (ADT) (slides)]<br />
* [http://free-electrons.com/pub/video/2011/elc/elc-2011-stewart-yocto-appdev-toolkit-x450p.webm The Yocto Project and its Application Development Toolkit (ADT) (450x800 video)]<br />
* [http://elinux.org/images/e/ec/Elc2011_flanagan.pdf Delivering Predictability: The Yocto Project Autobuilder, Automated Sanity Testing, License Collection, and Build Statistics Tracking (slides)]<br />
* [http://free-electrons.com/pub/video/2011/elc/elc-2011-flanagan-yocto-autobuilder-x450p.webm Delivering Predictability: The Yocto Project Autobuilder, Automated Sanity Testing, License Collection, and Build Statistics Tracking (450x800 video)]<br />
<br />
== Intel Developer Forum 2011 ==<br />
<br />
* Create a Custom Embedded Linux OS for Any Embedded Device Using the Yocto Project (hands-on lab)<br />
<br />
== Miscellaneous ==<br />
<br />
* [https://wiki.yoctoproject.org/wiki/images/e/e6/Custom_Users_Groups_in_Yocto1.1.pdf Using Custom Users/Groups in Yocto 1.1 (PDF slides, 2011-08-10)]</div>Sgarmanhttps://wiki.yoctoproject.org/wiki/index.php?title=Training&diff=3088Training2011-08-11T02:30:37Z<p>Sgarman: /* Miscellaneous */</p>
<hr />
<div>This page collects training materials as contributed by the community.<br />
<br />
== Embedded Linux Conference 2011 ==<br />
Thank you to Free-Electrons.com for the sweet contribution of these videos!<br />
<br />
[http://free-electrons.com/blog/elc-2011-videos/ Link to the Free-Electrons.com web page]<br />
<br />
* [http://elinux.org/images/7/7c/Elc2011_zanussi_wold.odp Building Custom Embedded Images with Yocto (slides)]<br />
* [http://free-electrons.com/pub/video/2011/elc/elc-2011-zanussi-wold-custom-embedded-images-yocto-x450p.webm Building Custom Embedded Images with Yocto (450x800 video)]<br />
* [https://wiki.yoctoproject.org/wiki/images/2/22/Elc11-yocto-kernel-tutorial.pdf Yocto Project: Practical Kernel Development Tutorial (slides)]<br />
* [http://free-electrons.com/pub/video/2011/elc/elc-2011-hart-yocto-kernel-development-x450p.webm Yocto Project: Practical Kernel Development Tutorial (450x800 video)]<br />
* [http://elinux.org/images/e/e6/ELC_Yocto_ADT_2011_davest.odp The Yocto Project and its Application Development Toolkit (ADT) (slides)]<br />
* [http://free-electrons.com/pub/video/2011/elc/elc-2011-stewart-yocto-appdev-toolkit-x450p.webm The Yocto Project and its Application Development Toolkit (ADT) (450x800 video)]<br />
* [http://elinux.org/images/e/ec/Elc2011_flanagan.pdf Delivering Predictability: The Yocto Project Autobuilder, Automated Sanity Testing, License Collection, and Build Statistics Tracking (slides)]<br />
* [http://free-electrons.com/pub/video/2011/elc/elc-2011-flanagan-yocto-autobuilder-x450p.webm Delivering Predictability: The Yocto Project Autobuilder, Automated Sanity Testing, License Collection, and Build Statistics Tracking (450x800 video)]<br />
<br />
== Miscellaneous ==<br />
<br />
* [https://wiki.yoctoproject.org/wiki/images/e/e6/Custom_Users_Groups_in_Yocto1.1.pdf Using Custom Users/Groups in Yocto 1.1 (PDF slides, 2011-08-10)]</div>Sgarmanhttps://wiki.yoctoproject.org/wiki/index.php?title=Training&diff=3087Training2011-08-11T02:29:40Z<p>Sgarman: </p>
<hr />
<div>This page collects training materials as contributed by the community.<br />
<br />
== Embedded Linux Conference 2011 ==<br />
Thank you to Free-Electrons.com for the sweet contribution of these videos!<br />
<br />
[http://free-electrons.com/blog/elc-2011-videos/ Link to the Free-Electrons.com web page]<br />
<br />
* [http://elinux.org/images/7/7c/Elc2011_zanussi_wold.odp Building Custom Embedded Images with Yocto (slides)]<br />
* [http://free-electrons.com/pub/video/2011/elc/elc-2011-zanussi-wold-custom-embedded-images-yocto-x450p.webm Building Custom Embedded Images with Yocto (450x800 video)]<br />
* [https://wiki.yoctoproject.org/wiki/images/2/22/Elc11-yocto-kernel-tutorial.pdf Yocto Project: Practical Kernel Development Tutorial (slides)]<br />
* [http://free-electrons.com/pub/video/2011/elc/elc-2011-hart-yocto-kernel-development-x450p.webm Yocto Project: Practical Kernel Development Tutorial (450x800 video)]<br />
* [http://elinux.org/images/e/e6/ELC_Yocto_ADT_2011_davest.odp The Yocto Project and its Application Development Toolkit (ADT) (slides)]<br />
* [http://free-electrons.com/pub/video/2011/elc/elc-2011-stewart-yocto-appdev-toolkit-x450p.webm The Yocto Project and its Application Development Toolkit (ADT) (450x800 video)]<br />
* [http://elinux.org/images/e/ec/Elc2011_flanagan.pdf Delivering Predictability: The Yocto Project Autobuilder, Automated Sanity Testing, License Collection, and Build Statistics Tracking (slides)]<br />
* [http://free-electrons.com/pub/video/2011/elc/elc-2011-flanagan-yocto-autobuilder-x450p.webm Delivering Predictability: The Yocto Project Autobuilder, Automated Sanity Testing, License Collection, and Build Statistics Tracking (450x800 video)]<br />
<br />
== Miscellaneous ==<br />
<br />
* [https://wiki.yoctoproject.org/wiki/images/e/e6/Custom_Users_Groups_in_Yocto1.1.pdf Using Custom Users/Groups in Yocto 1.1 (PDF slides)]</div>Sgarmanhttps://wiki.yoctoproject.org/wiki/index.php?title=File:Custom_Users_Groups_in_Yocto1.1.pdf&diff=3086File:Custom Users Groups in Yocto1.1.pdf2011-08-11T02:28:21Z<p>Sgarman: Presentation slides from "Creating Custom Users/Groups in Yocto 1.1"</p>
<hr />
<div>Presentation slides from "Creating Custom Users/Groups in Yocto 1.1"</div>Sgarmanhttps://wiki.yoctoproject.org/wiki/index.php?title=PAM_Integration&diff=2562PAM Integration2011-06-28T17:33:31Z<p>Sgarman: Created page with 'For Yocto 1.1 we are working to ensure that PAM (Pluggable Authentication Module) support is consistent and enabled in recipes where it is applicable. ==== Recipes with PAM sup…'</p>
<hr />
<div>For Yocto 1.1 we are working to ensure that PAM (Pluggable Authentication Module) support is consistent and enabled in recipes where it is applicable. <br />
<br />
==== Recipes with PAM support ====<br />
<br />
The following recipes were identified to have PAM support (some already implemented) on 2011-06-27:<br />
<br />
* at<br />
* consolekit<br />
* cronie<br />
* cups<br />
* dropbear<br />
* gnome-keyring<br />
* libcap<br />
* libuser<br />
* mc<br />
* openssh<br />
* polkit<br />
* screen<br />
* shadow<br />
* sudo<br />
* util-linux<br />
<br />
Note also:<br />
<br />
* The busybox box login has a option to use pam, but we use tinylogin's login right now (tinylogin also provides the su command)<br />
* gettext has a example file use pam in source code, I think it is just a example and don't need care<br />
* sysvinit has a patch contrib/notify-pam-dead.patch for /sbin/init to use pam , and it doesn't patched right now. And the package doesn't provide pam related configure option either.<br />
* In xserver-xf86-lite source code subdir os/utils checks #ifdef USE_PAM but there are no configure-time options for PAM.</div>Sgarmanhttps://wiki.yoctoproject.org/wiki/index.php?title=Processes_and_Activities&diff=2561Processes and Activities2011-06-28T17:27:46Z<p>Sgarman: </p>
<hr />
<div>Welcome to the Processes and Activities Page!<br />
<br />
* [[Recipe & Patch Style Guide]]<br />
* [[Distro Tracking]]<br />
* [[Best Known Methods (BKMs) for Package Updating]]<br />
* [[Working Behind a Network Proxy]]<br />
* [[SDK Generator]]<br />
* [[QA]]<br />
* [[Kernel]]<br />
* [[Core]]<br />
* [[Bugzilla Configuration and Bug Tracking]]<br />
* [[Yocto Release Engineering]]<br />
* [[Performance]]<br />
* [[Security]]<br />
* [[PAM Integration]]<br />
* [[Program Management Plan]]<br />
* [[Enable sstate cache]]</div>Sgarmanhttps://wiki.yoctoproject.org/wiki/index.php?title=Security&diff=1827Security2011-05-26T18:06:55Z<p>Sgarman: Created page with 'Since the Yocto Project is intended to be flexible and meet the needs of many applications, we leave policy-making decisions around security to our end users. Our goal instead is…'</p>
<hr />
<div>Since the Yocto Project is intended to be flexible and meet the needs of many applications, we leave policy-making decisions around security to our end users. Our goal instead is to ship each release with metadata that follows best practices in that we do not release recipe versions which are known to have significant security vulnerabilities. Generally this is done by upgrading recipes to newer versions that are no longer vulnerable to these issues. <br />
<br />
We are tracking security vulnerabilities in the Yocto Project against the [http://nvd.nist.gov/home.cfm National Vulnerability Database]. <br />
<br />
== Security Issues Addressed in Yocto 1.0.1 / Poky 5.0.1 ==<br />
<br />
The following security advisories are addressed in the Yocto Project 1.0.1 / Poky "Bernard" 5.0.1:<br />
<br />
* avahi: CVE-2011-1002<br />
* libexif: CVE-2007-6351, CVE-2007-6352, CVE-2009-3895<br />
* libxml2: CVE-2010-4008<br />
* openssl: CVE-2010-4180, CVE-2010-4252, CVE-2010-0014<br />
* rsync: CVE-2011-1097<br />
* rsync (GPLv2): CVE-2007-4091<br />
* rxvt-unicode: CVE-2006-0126<br />
* tar (GPLv2): CVE-2010-0624</div>Sgarmanhttps://wiki.yoctoproject.org/wiki/index.php?title=Processes_and_Activities&diff=1826Processes and Activities2011-05-26T17:57:32Z<p>Sgarman: </p>
<hr />
<div>Welcome to the Processes and Activities Page!<br />
<br />
* [[Recipe & Patch Style Guide]]<br />
* [[Distro Tracking]]<br />
* [[Best Known Methods (BKMs) for Package Updating]]<br />
* [[Working Behind a Network Proxy]]<br />
* [[SDK Generator]]<br />
* [[QA]]<br />
* [[Kernel]]<br />
* [[Core]]<br />
* [[Bugzilla Configuration and Bug Tracking]]<br />
* [[Yocto Release Engineering]]<br />
* [[Performance]]<br />
* [[Security]]<br />
* [[Program Management Plan]]<br />
* [[Enable sstate cache]]</div>Sgarmanhttps://wiki.yoctoproject.org/wiki/index.php?title=YoctoCalendar&diff=1628YoctoCalendar2011-05-06T17:30:23Z<p>Sgarman: /* Mozilla Thunderbird Lightning */</p>
<hr />
<div>__TOC__<br />
<br />
In an effort to make the Yocto Project development schedule as accessible as possible, we are experimenting with a series of web calendars which can be [https://www.google.com/calendar/embed?height=600&amp;wkst=1&amp;bgcolor=%23FFFFFF&amp;src=sc7rov4ck552t2f0pav120t7r0%40group.calendar.google.com&amp;color=%23528800&amp;src=nbpncuc2molpa72g031br68pmg%40group.calendar.google.com&amp;color=%23125A12&amp;src=e0ji72ort30nioi6clvd9jru6s%40group.calendar.google.com&amp;color=%238C500B&amp;src=3a0927ctps51u8rs2jv1uligdc%40group.calendar.google.com&amp;color=%23691426&amp;src=theyoctoproject%40gmail.com&amp;color=%23182C57&amp;ctz=America%2FLos_Angeles viewed online], or incorporated into your preferred calendaring application.<br />
<br />
The following image is a preview of what sort of information this set of calendars provide. You can click on the preview to view the actual calendar in your browser.<br />
<br />
[[File:Yocto-calendar-preview.png|link=https://www.google.com/calendar/embed?height=600&wkst=1&bgcolor=%23FFFFFF&src=sc7rov4ck552t2f0pav120t7r0%40group.calendar.google.com&color=%23528800&src=nbpncuc2molpa72g031br68pmg%40group.calendar.google.com&color=%23125A12&src=e0ji72ort30nioi6clvd9jru6s%40group.calendar.google.com&color=%238C500B&src=3a0927ctps51u8rs2jv1uligdc%40group.calendar.google.com&color=%23691426&src=theyoctoproject%40gmail.com&color=%23182C57&ctz=America%2FLos_Angeles]]<br />
<br />
TODO: Find a way to embed the actual calendar in this page using the following iframe tag.<br />
<br />
<iframe src="https://www.google.com/calendar/embed?height=600&amp;wkst=1&amp;bgcolor=%23FFFFFF&amp;src=sc7rov4ck552t2f0pav120t7r0%40group.calendar.google.com&amp;color=%23528800&amp;src=nbpncuc2molpa72g031br68pmg%40group.calendar.google.com&amp;color=%23125A12&amp;src=e0ji72ort30nioi6clvd9jru6s%40group.calendar.google.com&amp;color=%238C500B&amp;src=3a0927ctps51u8rs2jv1uligdc%40group.calendar.google.com&amp;color=%23691426&amp;src=theyoctoproject%40gmail.com&amp;color=%23182C57&amp;ctz=America%2FLos_Angeles" style=" border-width:0 " width="800" height="600" frameborder="0" scrolling="no"></iframe><br />
<br />
== Using the Calendars ==<br />
With the ICS URLs provided below, these calendars can be embedded in your preferred calendaring program. They have been tested and known to work with Google Calendar, Microsoft Outlook, and Thunderbird Lightning.<br />
<br />
=== Google Calendar ===<br />
The easiest way to add these calendars to your Google Calendar is to click on the "view online" link in the opening paragraph (FIXME: eventually reference the embedded calendar) and then click on the "(+ Google Calendar)" image in the lower right hand corner of the screen. This will bring up a dialog allowing you to select which of all The Yocto Project related calendars you would like to add.<br />
<br />
Alternatively, you can add them individually using the ICS link below in the Google Calendar application by selecting Add (under Other calendars), Add by URL, and then entering the ICS URL.<br />
<br />
=== Microsoft Outlook ===<br />
For details on using Google Calendars with Microsoft Outlook, give the following links a try:<br />
* [http://www.howtogeek.com/howto/microsoft-office/view-your-google-calendar-in-outlook-2007/ View Your Google Calendar in Outlook 2007]<br />
* [http://www.howtogeek.com/howto/18353/view-your-google-calendar-in-outlook-2010/ View Your Google Calendar in Outlook 2010]<br />
<br />
Note that in order to get the calendar to actually synchronize, it may be necessary to define a special Send/Receive group that includes the internet calendar subscriptions and make sure it is included in send/receive.<br />
* Microsoft Outlook 2007<br />
** Tools -> Send/Receive -> Send/Receive Settings -> Define Send/Receive Groups...<br />
** Check "Include this group in send/receive (F9)."<br />
<br />
=== Mozilla Thunderbird Lightning ===<br />
To add a Google Calendar to Mozilla Thunderbird's Lightning extension:<br />
* Right click in the calendar area and select "New Calendar"<br />
* Choose "On the Network" and click Next<br />
* Select "iCalendar (ICS)" format<br />
* Enter the ICS URL and click Next<br />
* Enter the calendar's name (replacing "basic")<br />
<br />
Note: The next time you start a new Thunderbird session, a dialog box will pop up asking if you'd like to update any of the calendars you subscribed to. This doesn't do what you think it will do - select no. Otherwise you'll get a series of login dialogs to access the gmail account they were created with.<br />
<br />
== Calendar URLs ==<br />
* Yocto Events<br />
** ICS: https://www.google.com/calendar/ical/theyoctoproject%40gmail.com/public/basic.ics<br />
* Yocto 1.0.1 Schedule<br />
** ICS: https://www.google.com/calendar/ical/e0ji72ort30nioi6clvd9jru6s%40group.calendar.google.com/public/basic.ics<br />
* Yocto 1.1 Schedule<br />
** ICS: https://www.google.com/calendar/ical/3a0927ctps51u8rs2jv1uligdc%40group.calendar.google.com/public/basic.ics<br />
* QA 1.0.1 Tasks<br />
** ICS: https://www.google.com/calendar/ical/sc7rov4ck552t2f0pav120t7r0%40group.calendar.google.com/public/basic.ics<br />
* QA 1.1 Tasks<br />
** ICS: https://www.google.com/calendar/ical/nbpncuc2molpa72g031br68pmg%40group.calendar.google.com/public/basic.ics</div>Sgarmanhttps://wiki.yoctoproject.org/wiki/index.php?title=Best_Known_Methods_(BKMs)_for_Package_Updating&diff=408Best Known Methods (BKMs) for Package Updating2011-01-05T17:16:57Z<p>Sgarman: /* Distro Tracking Fields */</p>
<hr />
<div>This page is used for capturing the Best Known Methods (BKMs) of package upgrading as we get reviewed and process more of the packages.<br />
<br />
== Don't Retain older Versions ==<br />
<br />
Unless there is a specific need (which will probably occur for GPLv2, this has also happened in the past when platforms have known bugs in the latest version) don't retain older versions of the recipe files and patches.<br />
<br />
== Use git mv to rename recipe and patches ==<br />
<br />
From Josh:<br />
Generally the way I perform recipe upgrades is to use git mv to rename the old file to the new version, this means that you don't have to consciously delete the old version later (win 1) and that git tracks the rename and the differences with the old file, which doesn't happen with a delete and add (win 2).<br />
<br />
The advantage of this is that you and any reviewers can more easily see what has changed with the updated version of the recipe.<br />
<br />
<br />
Nitin: Actually {git mv a b} is nothing but {mv a b; git rm a; git add b} And the file renames are detected by git automatically by looking at the file contents. Because of this git behavior, git shows some renames as renames and sometimes not. And I did not find a way to force git to understand renames. So if after "git mv" git is showing "file add & file remove", then don't get surprised, it's normal git operation.<br />
<br />
=== Reset PR to 0 (or add PR) when upgrading recipes ===<br />
<br />
This is a good visual reminder to bump in the future if needed.<br />
<br />
== For upgrades it's ok to use OE for inspiration ==<br />
<br />
When upgrading packages, do the git mv as above, and build if it breaks, it's OK to check the OE equivalent and grab new patch or configuration change, just don't grab the whole recipe.<br />
<br />
Be sure to add a credit to OE in your commit message when you do take a change like this.<br />
<br />
Review: [[Merging packages from OpenEmbedded]]<br />
<br />
== For new package grab OE version, but sanitize them ==<br />
<br />
Follow the recipe rules for Yocto when you take an OE recipe, be sure to clean all the OE'isms out<br />
<br />
Again, give credit to OE in commit messages<br />
<br />
Review: [[Merging packages from OpenEmbedded]]<br />
<br />
== Do NOT Merge .inc / .bb files ==<br />
<br />
This was a decision that slipped by me, and was not communicated well, we do not want to merge the common ".inc" files and recipe (.bb) files. This is the case even if the .bb only contains a require and a PR="r0" line. This does not mean split everything at this point, but don't merge going forward.<br />
<br />
== White Space Management ==<br />
<br />
<br />
* Most variables such as SRC_URI should use spaces.<br />
<br />
* Shell functions should use tabs<br />
<br />
* Python functions should use spaces (4 spaces per indent).<br />
<br />
== Commenting in Patches ==<br />
<br />
When you change or add patches, be sure to include attributions of where the patch came from, along with your full name and email similar to "Signed-off-by", no special tag is needed (yet?), but having your full name and email is important to track it.<br />
<br />
== New style patch application ==<br />
<br />
The patch and pnum parameters have been renamed to the more logical apply and striplevel. The apply parameter takes either "yes" or "no" and the striplevel parameter takes an integer (0, 1, etc).<br />
<br />
Both parameters are now optional with "sane" defaults.<br />
<br />
The apply parameter is optional for SRC_URI lines with patch or diff extensions, which will default to being applied.<br />
<br />
The striplevel parameter is also optional with a default striplevel of 1.<br />
<br />
Old style parameters (patch and pnum) will continue to work for some time but it would be useful to move to the new style syntax as people are updating other parts of their recipes.<br />
<br />
Therefore a patch line would be changed from:<br />
<br />
file://some.patch;patch=1;pnum=2<br />
<br />
to: <br />
<br />
file://some.patch;striplevel=2 <br />
<br />
and a patch line:<br />
<br />
file://another.diff;patch=1;pnum=1<br />
<br />
could be changed to:<br />
<br />
file://another.diff <br />
<br />
== Recipe Metadata Updates ==<br />
<br />
=== DESCRIPTION and SUMMARY ===<br />
<br />
<Mark Hatle Can you please comment here><br />
<br />
=== LICENSE Metadata ===<br />
<br />
* The LICENSE information in the .bb file needs to be practical.<br />
* if there's "or any later version" in GPL related copyright, append "+" then which effectively means below:<br />
GPLv2, GPLv2+, GPLv3, GPLv3+, LGPLv2, LGPLv2+, LGPLv2.1, LGPLv2.1+, LGPLv3, LGPLv3+<br />
* Scripts generated by autotools are not counted for licensing (they are always under GPL)<br />
* Dual license: GPLv2 | BSD<br />
* Multiple licenses: GPLv3+ & LGPLv2.1+<br />
* GPLv3 (correction may be required!)<br />
anti-tivoization in GPLv3 only applies to User Products, which per definition is “either <br />
(1) a “consumer product”, which means any tangible personal property which is normally <br />
used for personal, family, or household purposes, or (2) anything designed or sold for <br />
incorporation into a dwelling."<br />
* For package changing its license, better to keep new license in .inc file with old license in corresponding .bb file. Take readline for example:<br />
readline.inc: LICENSE = "GPLv3+"<br />
readline_5.2.bb: LICENSE = "GPLv2"<br />
* we can treat MIT-style license as "MIT", meaning that any lawyer can tell it derivatives from standard form, such as below one:<br />
<br />
Permission to use, copy, modify, distribute, and sell this software and its<br />
documentation for any purpose is hereby granted without fee, provided that<br />
the above copyright notice appear in all copies and that both that copyright<br />
notice and this permission notice appear in supporting documentation, and<br />
that the name of the copyright holders not be used in advertising or<br />
publicity pertaining to distribution of the software without specific,<br />
written prior permission. The copyright holders make no representations<br />
about the suitability of this software for any purpose. It is provided "as<br />
is" without express or implied warranty.<br />
* some package may have complex license, such as wireless-tool:<br />
most of files are GPLv2; <br />
one part in file is GPLv2+; <br />
some of them are dual licensed, such as sample_enc.c under LGPL | MPL | BSD.<br />
In such case, first ignore the GPLv2+ bit since there is no way you could ever ship the package under say GPLv3 due to many headers being v2 only.<br />
Since there are files that are GPLv2 only, the answer is no. The LICENSE field is therefore primarily GPLv2 and we can ignore the 2+ bits.<br />
If they're a key part, the recipe becomes "GPLv2 & (LGPL | MPL | BSD)"<br />
* automake may generate COPYING automatically if there's no such one existing (e.g. Xsettings-client-0.10). A short answer is to add a MIT-style COPYING in poky and then install it before autotools work. See last section for detail description<br />
* all .bb files require LICENSE fields, even for those Poky specific (which are MIT).<br />
* ask on the ML for license information for those local files we don't know their origins<br />
* Name Sub-Packages with different Licenses<br />
** LICENSE = "LGPLv2.1 & GPLv3+"<br />
** LICENSE_libidn = "LGPLv2.1"<br />
** LICENSE_libidn-tests = "GPLv3+"<br />
* when listing sub-package license, remember to use names included in PACKAGES instead of source directories, e.g:<br />
LICENSE = "GPLv2 & LGPLv2 & BSD & MIT"<br />
LICENSE_lib/ext2fs = "LGPLv2"<br />
<br />
Better to use:<br />
LICENSE_e2fsprogs-mke2fs = "LGPLv2"<br />
because mke2fs is a package name<br />
----<br />
* Two variants of the license, the New BSD License/Modified BSD License, and the Simplified BSD License/FreeBSD License have been verified as GPL-compatible free software licenses by the Free Software Foundation, while the original has not been accepted as an open source license(http://en.wikipedia.org/wiki/Original_BSD_license#4-clause)<br />
* The original BSD license also includes a clause requiring all advertising of the software to display a notice crediting its authors. This "advertising clause" (since disavowed by UC Berkeley) is present in the modified MIT License used by XFree86 (http://en.wikipedia.org/wiki/MIT_License)<br />
* http://en.wikipedia.org/wiki/Comparison_of_free_software_licenses<br />
* http://www.opensource.org/licenses/alphabetical<br />
* http://www.gnu.org/licenses/license-list.html<br />
<br />
==== Autotools adds wrong COPYING ====<br />
<br />
Autotools add the wrong COPYING license to source code with out COPYING, to ensure that we have the correct and consistent license, add the correct license file to the SRC_URI List and a do_config_prepend().<br />
<br />
SRC_URI = "... \<br />
...<br />
file://XXX-license"<br />
<br />
do_configure_prepend() {<br />
# This package doesn't ship with its own COPYING file and <br />
# autotools will install a GPLv2 one instead of MIT. Add the<br />
# correct license here to avoid confusion.<br />
cp ${WORKDIR}/MIT-style-license ${S}/COPYING<br />
}<br />
<br />
== Distro Tracking Fields ==<br />
<br />
The file meta/conf/distro/include/distro_tracking_fields.inc exists to allow us to track various pieces of information about recipes and upstream versions (e.g, recipe maintainer contact information, date of latest upstream release, alternate names used for this recipe in other Linux distros, etc). The following defines the meaning of each field:<br />
<br />
;RECIPE_STATUS<br />
: Indicates whether the recipe has been reviewed for basic quality control information (e.g, has had its software license verified). "red" indicates these checks have not been done, and "green" indicates that they have been done.<br />
;RECIPE_DEPENDENCY_CHECK<br />
: Indicates whether the recipe has been built from scratch to verify that all of its build and runtime dependencies have been specified. Value is either "not done" or "done"<br />
;RECIPE_LATEST_VERSION<br />
: The latest upstream stable version, "3.0"<br />
;RECIPE_NO_OF_PATCHES<br />
: The number of patches we ship with the recipe.<br />
;RECIPE_PATCH<br />
: Summarizes the purpose of each patch associated with a recipe.<br />
;RECIPE_LATEST_RELEASE_DATE<br />
: The date at which the latest upstream stable version (mentioned in RECIPE_LATEST_VERSION) was released, "03/2010"<br />
;RECIPE_TIME_BETWEEN_LAST_TWO_RELEASES<br />
: The amount of time which passed between the most recent two upstream stable releases, "2 months"<br />
;RECIPE_COMMENTS<br />
: A field to mention comments, such as why a recipe can't be brought up to the latest upstream release, or unusual build issues that need to be worked around.<br />
;RECIPE_LAST_UPDATE<br />
: Date of the last changes to the recipe, "Dec 10, 2010"<br />
;RECIPE_MAINTAINER<br />
: Name and email address of the person maintaining the recipe, "Firstname Lastname <email.address>"<br />
<br />
Note that in the file, each field name is appended with -pn-<recipe name>.</div>Sgarmanhttps://wiki.yoctoproject.org/wiki/index.php?title=Best_Known_Methods_(BKMs)_for_Package_Updating&diff=407Best Known Methods (BKMs) for Package Updating2011-01-05T17:13:25Z<p>Sgarman: Added definitions of distro tracking fields</p>
<hr />
<div>This page is used for capturing the Best Known Methods (BKMs) of package upgrading as we get reviewed and process more of the packages.<br />
<br />
== Don't Retain older Versions ==<br />
<br />
Unless there is a specific need (which will probably occur for GPLv2, this has also happened in the past when platforms have known bugs in the latest version) don't retain older versions of the recipe files and patches.<br />
<br />
== Use git mv to rename recipe and patches ==<br />
<br />
From Josh:<br />
Generally the way I perform recipe upgrades is to use git mv to rename the old file to the new version, this means that you don't have to consciously delete the old version later (win 1) and that git tracks the rename and the differences with the old file, which doesn't happen with a delete and add (win 2).<br />
<br />
The advantage of this is that you and any reviewers can more easily see what has changed with the updated version of the recipe.<br />
<br />
<br />
Nitin: Actually {git mv a b} is nothing but {mv a b; git rm a; git add b} And the file renames are detected by git automatically by looking at the file contents. Because of this git behavior, git shows some renames as renames and sometimes not. And I did not find a way to force git to understand renames. So if after "git mv" git is showing "file add & file remove", then don't get surprised, it's normal git operation.<br />
<br />
=== Reset PR to 0 (or add PR) when upgrading recipes ===<br />
<br />
This is a good visual reminder to bump in the future if needed.<br />
<br />
== For upgrades it's ok to use OE for inspiration ==<br />
<br />
When upgrading packages, do the git mv as above, and build if it breaks, it's OK to check the OE equivalent and grab new patch or configuration change, just don't grab the whole recipe.<br />
<br />
Be sure to add a credit to OE in your commit message when you do take a change like this.<br />
<br />
Review: [[Merging packages from OpenEmbedded]]<br />
<br />
== For new package grab OE version, but sanitize them ==<br />
<br />
Follow the recipe rules for Yocto when you take an OE recipe, be sure to clean all the OE'isms out<br />
<br />
Again, give credit to OE in commit messages<br />
<br />
Review: [[Merging packages from OpenEmbedded]]<br />
<br />
== Do NOT Merge .inc / .bb files ==<br />
<br />
This was a decision that slipped by me, and was not communicated well, we do not want to merge the common ".inc" files and recipe (.bb) files. This is the case even if the .bb only contains a require and a PR="r0" line. This does not mean split everything at this point, but don't merge going forward.<br />
<br />
== White Space Management ==<br />
<br />
<br />
* Most variables such as SRC_URI should use spaces.<br />
<br />
* Shell functions should use tabs<br />
<br />
* Python functions should use spaces (4 spaces per indent).<br />
<br />
== Commenting in Patches ==<br />
<br />
When you change or add patches, be sure to include attributions of where the patch came from, along with your full name and email similar to "Signed-off-by", no special tag is needed (yet?), but having your full name and email is important to track it.<br />
<br />
== New style patch application ==<br />
<br />
The patch and pnum parameters have been renamed to the more logical apply and striplevel. The apply parameter takes either "yes" or "no" and the striplevel parameter takes an integer (0, 1, etc).<br />
<br />
Both parameters are now optional with "sane" defaults.<br />
<br />
The apply parameter is optional for SRC_URI lines with patch or diff extensions, which will default to being applied.<br />
<br />
The striplevel parameter is also optional with a default striplevel of 1.<br />
<br />
Old style parameters (patch and pnum) will continue to work for some time but it would be useful to move to the new style syntax as people are updating other parts of their recipes.<br />
<br />
Therefore a patch line would be changed from:<br />
<br />
file://some.patch;patch=1;pnum=2<br />
<br />
to: <br />
<br />
file://some.patch;striplevel=2 <br />
<br />
and a patch line:<br />
<br />
file://another.diff;patch=1;pnum=1<br />
<br />
could be changed to:<br />
<br />
file://another.diff <br />
<br />
== Recipe Metadata Updates ==<br />
<br />
=== DESCRIPTION and SUMMARY ===<br />
<br />
<Mark Hatle Can you please comment here><br />
<br />
=== LICENSE Metadata ===<br />
<br />
* The LICENSE information in the .bb file needs to be practical.<br />
* if there's "or any later version" in GPL related copyright, append "+" then which effectively means below:<br />
GPLv2, GPLv2+, GPLv3, GPLv3+, LGPLv2, LGPLv2+, LGPLv2.1, LGPLv2.1+, LGPLv3, LGPLv3+<br />
* Scripts generated by autotools are not counted for licensing (they are always under GPL)<br />
* Dual license: GPLv2 | BSD<br />
* Multiple licenses: GPLv3+ & LGPLv2.1+<br />
* GPLv3 (correction may be required!)<br />
anti-tivoization in GPLv3 only applies to User Products, which per definition is “either <br />
(1) a “consumer product”, which means any tangible personal property which is normally <br />
used for personal, family, or household purposes, or (2) anything designed or sold for <br />
incorporation into a dwelling."<br />
* For package changing its license, better to keep new license in .inc file with old license in corresponding .bb file. Take readline for example:<br />
readline.inc: LICENSE = "GPLv3+"<br />
readline_5.2.bb: LICENSE = "GPLv2"<br />
* we can treat MIT-style license as "MIT", meaning that any lawyer can tell it derivatives from standard form, such as below one:<br />
<br />
Permission to use, copy, modify, distribute, and sell this software and its<br />
documentation for any purpose is hereby granted without fee, provided that<br />
the above copyright notice appear in all copies and that both that copyright<br />
notice and this permission notice appear in supporting documentation, and<br />
that the name of the copyright holders not be used in advertising or<br />
publicity pertaining to distribution of the software without specific,<br />
written prior permission. The copyright holders make no representations<br />
about the suitability of this software for any purpose. It is provided "as<br />
is" without express or implied warranty.<br />
* some package may have complex license, such as wireless-tool:<br />
most of files are GPLv2; <br />
one part in file is GPLv2+; <br />
some of them are dual licensed, such as sample_enc.c under LGPL | MPL | BSD.<br />
In such case, first ignore the GPLv2+ bit since there is no way you could ever ship the package under say GPLv3 due to many headers being v2 only.<br />
Since there are files that are GPLv2 only, the answer is no. The LICENSE field is therefore primarily GPLv2 and we can ignore the 2+ bits.<br />
If they're a key part, the recipe becomes "GPLv2 & (LGPL | MPL | BSD)"<br />
* automake may generate COPYING automatically if there's no such one existing (e.g. Xsettings-client-0.10). A short answer is to add a MIT-style COPYING in poky and then install it before autotools work. See last section for detail description<br />
* all .bb files require LICENSE fields, even for those Poky specific (which are MIT).<br />
* ask on the ML for license information for those local files we don't know their origins<br />
* Name Sub-Packages with different Licenses<br />
** LICENSE = "LGPLv2.1 & GPLv3+"<br />
** LICENSE_libidn = "LGPLv2.1"<br />
** LICENSE_libidn-tests = "GPLv3+"<br />
* when listing sub-package license, remember to use names included in PACKAGES instead of source directories, e.g:<br />
LICENSE = "GPLv2 & LGPLv2 & BSD & MIT"<br />
LICENSE_lib/ext2fs = "LGPLv2"<br />
<br />
Better to use:<br />
LICENSE_e2fsprogs-mke2fs = "LGPLv2"<br />
because mke2fs is a package name<br />
----<br />
* Two variants of the license, the New BSD License/Modified BSD License, and the Simplified BSD License/FreeBSD License have been verified as GPL-compatible free software licenses by the Free Software Foundation, while the original has not been accepted as an open source license(http://en.wikipedia.org/wiki/Original_BSD_license#4-clause)<br />
* The original BSD license also includes a clause requiring all advertising of the software to display a notice crediting its authors. This "advertising clause" (since disavowed by UC Berkeley) is present in the modified MIT License used by XFree86 (http://en.wikipedia.org/wiki/MIT_License)<br />
* http://en.wikipedia.org/wiki/Comparison_of_free_software_licenses<br />
* http://www.opensource.org/licenses/alphabetical<br />
* http://www.gnu.org/licenses/license-list.html<br />
<br />
==== Autotools adds wrong COPYING ====<br />
<br />
Autotools add the wrong COPYING license to source code with out COPYING, to ensure that we have the correct and consistent license, add the correct license file to the SRC_URI List and a do_config_prepend().<br />
<br />
SRC_URI = "... \<br />
...<br />
file://XXX-license"<br />
<br />
do_configure_prepend() {<br />
# This package doesn't ship with its own COPYING file and <br />
# autotools will install a GPLv2 one instead of MIT. Add the<br />
# correct license here to avoid confusion.<br />
cp ${WORKDIR}/MIT-style-license ${S}/COPYING<br />
}<br />
<br />
== Distro Tracking Fields ==<br />
<br />
The file meta/conf/distro/include/distro_tracking_fields.inc exists to allow us to track various pieces of information about recipes and upstream versions (e.g, recipe maintainer contact information, date of latest upstream release, alternate names used for this recipe in other Linux distros, etc). The following defines the meaning of each field:<br />
<br />
;RECIPE_STATUS<br />
: Indicates whether the recipe has been reviewed for basic quality control information (e.g, has had its software license verified). "red" indicates these checks have not been done, and "green" indicates that they have been done.<br />
;RECIPE_DEPENDENCY_CHECK<br />
: Indicates whether the recipe has been built from scratch to verify that all of its build and runtime dependencies have been specified. Value is either "not done" or "done"<br />
;RECIPE_LATEST_VERSION<br />
: The latest upstream stable version, "3.0"<br />
;RECIPE_NO_OF_PATCHES<br />
: The number of patches we ship with the recipe.<br />
;RECIPE_PATCH<br />
: Summarizes the purpose of each patch associated with a recipe.<br />
;RECIPE_LATEST_RELEASE_DATE<br />
: The date at which the upstream stable release (mentioned in RECIPE_LATEST_VERSION) was released, "03/2010"<br />
;RECIPE_TIME_BETWEEN_LAST_TWO_RELEASES<br />
: The amount of time which passed between the most recent two upstream stable releases, "2 months"<br />
;RECIPE_COMMENTS<br />
: A field to mention comments, such as why a recipe can't be brought up to the latest upstream release, or unusual build issues that need to be worked around.<br />
;RECIPE_LAST_UPDATE<br />
: Date of the last changes to the recipe, "Dec 10, 2010"<br />
;RECIPE_MAINTAINER<br />
: Name and email address of the person maintaining the recipe, "Firstname Lastname <email.address>"<br />
<br />
Note that in the file, each field name is appended with -pn-<recipe name>.</div>Sgarmanhttps://wiki.yoctoproject.org/wiki/index.php?title=Enabling_Automation_Test_in_Poky&diff=350Enabling Automation Test in Poky2010-12-14T18:53:11Z<p>Sgarman: </p>
<hr />
<div>=== Enable Automation Test in Poky ===<br />
Currently we have implemented a handful automated sanity test cases in Poky (boot/ssh/dmesg/shutdown). A user can follow the below steps to enable the runtime automation test:<br />
<br />
* Make sure your working tree has latest test code from master. This feature was not part of the 0.9 release (but will be included in 1.0)<br />
* Make sure your machine has the "expect" package installed. The package is necessary for testing. We will add a recipe for it later. Currently, you need install it by yourself. On Ubuntu host, you can use apt-get to install expect:<br />
<pre><br />
$ apt-get install expect<br />
</pre><br />
* Edit /etc/sudoers to allow the user run sudo without prompted for a password. For example, you can do like following for user "tester":<br />
<pre><br />
$ cat /etc/sudoers<br />
# /etc/sudoers<br />
#<br />
# This file MUST be edited with the 'visudo' command as root.<br />
#<br />
# See the man page for details on how to write a sudoers file.<br />
#<br />
....<br />
....<br />
....<br />
<br />
%tester ALL=(ALL) NOPASSWD: NOPASSWD: ALL<br />
</pre><br />
* Instead of requiring sudo access, you can run the poky-gen-tapdevs script from a build of meta-ide-support or a Poky toolchain install. This is recommended for more security-conscious environments. The script will create and set up networking for one or more tap devices that will be used automatically by the poky-qemu script if detected, and it will no longer require root access.<br />
* Typically, you need a X environment to start QEMU. You can use your desktop's DISPLAY. Or, alternatively, you can install vncserver, and startup a X environment in localhost:x.0. (x can be 1, 2, 3.....n)<br />
* For the VNC setup, the following xstartup script is known to work for an openSUSE 11.2 host:<br />
<pre><br />
#!/bin/sh<br />
<br />
xrdb $HOME/.Xresources<br />
xsetroot -solid grey<br />
xhost +<br />
xterm -geometry 80x24+10+10 -ls -title "$VNCDESKTOP Desktop" &<br />
twm &<br />
</pre><br />
* For the VNC setup, you will also want to put the following in ~/.twmrc, which allows windows to be placed automatically.<br />
<pre><br />
RandomPlacement<br />
</pre><br />
* You need set "IMAGETEST" to "qemu" in build/conf/local.conf<br />
<pre><br />
$ cat local.conf<br />
.....<br />
# Set IMAGETEST to qemu if you want to build testcases and start<br />
# testing in qemu after do_rootfs.<br />
IMAGETEST = "qemu"<br />
.....<br />
</pre><br />
* Then you can run "bitbake poky-image-xxx" (xxx can be minimal, sato, sdk). After the kernel/image are generated, you need run "bitbake poky-image-xxx -c qemuimagetest". It will trigger automation test and you will get the result after a while. :)</div>Sgarmanhttps://wiki.yoctoproject.org/wiki/index.php?title=Enabling_Automation_Test_in_Poky&diff=280Enabling Automation Test in Poky2010-11-12T07:11:13Z<p>Sgarman: Added some important details to sanity test automation regarding VNC setup</p>
<hr />
<div>=== Enable Automation Test in Poky ===<br />
Currently we have implemented two automated sanity test cases in Poky. User can follow below steps to enable the automation test:<br />
<br />
* Make sure your working tree has latest test code. The first sanity test implementation is checked in poky master tree as commit, '''fd1d661b391dfad1edaac937a17c1165f635031a.<br />
* Make sure your machine has package "expect" installed. The package is necessary for testing. We will add a recipe for it later. Currently, you need install it by yourself. On Ubuntu host, you can use apt-get to install expect:<br />
<pre><br />
$ apt-get install expect<br />
</pre><br />
* Edit /etc/sudoers to allow the user run sudo without prompted for a password. For example, you can do like following for user "tester":<br />
<pre><br />
$ cat /etc/sudoers<br />
# /etc/sudoers<br />
#<br />
# This file MUST be edited with the 'visudo' command as root.<br />
#<br />
# See the man page for details on how to write a sudoers file.<br />
#<br />
....<br />
....<br />
....<br />
<br />
%tester ALL=(ALL) NOPASSWD: NOPASSWD: ALL<br />
</pre><br />
* Instead of requiring sudo access, you can run the poky-gen-tapdevs script from a build of meta-ide-support or a Poky toolchain install in /opt/poky. The script will create and set up networking for one or more tap devices that will be used automatically by the poky-qemu script if detected.<br />
* Typically, you need a X environment to start QEMU. You can use your desktop's DISPLAY. Or, alternatively, you can install vncserver, and startup a X environment in localhost:x.0. (x can be 1, 2, 3.....n)<br />
* For the VNC setup, the following xstartup script is known to work for an openSUSE 11.2 host:<br />
<pre><br />
#!/bin/sh<br />
<br />
xrdb $HOME/.Xresources<br />
xsetroot -solid grey<br />
xhost +<br />
xterm -geometry 80x24+10+10 -ls -title "$VNCDESKTOP Desktop" &<br />
twm &<br />
</pre><br />
* For the VNC setup, you will also want to put the following in ~/.twmrc, which allows windows to be placed automatically.<br />
<pre><br />
RandomPlacement<br />
</pre><br />
* You need set "IMAGETEST" to "qemu" in build/conf/local.conf<br />
<pre><br />
$ cat local.conf<br />
.....<br />
# Set IMAGETEST to qemu if you want to build testcases and start<br />
# testing in qemu after do_rootfs.<br />
IMAGETEST = "qemu"<br />
.....<br />
</pre><br />
* Then you can run "bitbake poky-image-xxx" (xxx can be minimal, sato, sdk). After the kernel/image are generated, you need run "bitbake poky-image-xxx -c qemuimagetest". It will trigger automation test and you will get the result after a while. :)</div>Sgarmanhttps://wiki.yoctoproject.org/wiki/index.php?title=Working_Behind_a_Network_Proxy&diff=266Working Behind a Network Proxy2010-11-09T18:01:01Z<p>Sgarman: Added proxy configuration guide</p>
<hr />
<div>This page lists some configuration tips for working behind a proxy.<br />
<br />
== HTTP/HTTPS/FTP Setup ==<br />
<br />
Set the following environment variables in your ~/.bashrc file. This example uses the same proxy server and port number for all three protocols.<br />
<br />
export http_proxy='http://myproxy.example.com:1080/'<br />
export https_proxy='https://myproxy.example.com:1080/'<br />
export ftp_proxy='http://myproxy.example.com:1080/'<br />
<br />
== Git Setup ==<br />
<br />
First make sure you have the netcat utility (nc) installed on your host.<br />
<br />
Create a script named ''git-proxy'' and put it in /usr/local/bin:<br />
<br />
#!/bin/bash<br />
<br />
PROXY=myproxy.example.com<br />
PORT=1080<br />
<br />
case $1 in<br />
# list internal git servers here that you do not want to use<br />
# the proxy with, separated by a pipe character '|' as below:<br />
internalgit1.example.com|internalgit2.example.com)<br />
METHOD="-X connect"<br />
;;<br />
*)<br />
METHOD="-X 5 -x ${PROXY}:${PORT}"<br />
;;<br />
esac<br />
<br />
/usr/bin/nc $METHOD $*<br />
<br />
Note that on some Linux distros, the nc binary is in /bin. You can also change the '5' in the second METHOD line to '4' if your proxy server only supports SOCKS v4.<br />
<br />
Then set the environment variable GIT_PROXY_COMMAND in your ~/.bashrc file and point it to this script:<br />
<br />
export GIT_PROXY_COMMAND=/usr/local/bin/git-proxy<br />
<br />
== Subversion Setup ==<br />
<br />
You'll need to have the following in your ~/.subversion/servers file:<br />
<br />
[global]<br />
http-proxy-exceptions = *.exception.com, www.internal-site.org<br />
http-proxy-host = myproxy.example.com<br />
http-proxy-port = 1080<br />
<br />
You can also set ''http-proxy-username'' and ''http-proxy-password'' if your proxy requires authentication.<br />
<br />
== CVS Setup ==<br />
<br />
For CVS checkouts to work correctly, you need to add some options in your Poky ''local.conf'' file.<br />
<br />
CVS_PROXY_HOST = "myproxy.example.com"<br />
CVS_PROXY_PORT = "1080"</div>Sgarmanhttps://wiki.yoctoproject.org/wiki/index.php?title=Processes_and_Activities&diff=265Processes and Activities2010-11-09T17:19:25Z<p>Sgarman: </p>
<hr />
<div>Welcome to the Processes and Activities Page!<br />
<br />
* [[BKMs for Package Updating]]<br />
* [[Working Behind a Network Proxy]]<br />
* [[SDK Generator]]<br />
* [[QA]]<br />
* [[Kernel]]<br />
* [[Core]]<br />
* [[Bugzilla Configuration and Bug Tracking]]<br />
* [[Yocto Release Engineering]]</div>Sgarmanhttps://wiki.yoctoproject.org/wiki/index.php?title=User:Sgarman&diff=245User:Sgarman2010-10-29T07:33:11Z<p>Sgarman: Created my user page</p>
<hr />
<div>Scott Garman<br />
<br />
* Embedded Linux Distro Engineer at Intel<br />
* IRC Nick: zenlinuxPDX<br />
* Blog (personal): http://blog.zenlinux.com<br />
* Email: scott dot a dot garman at intel dot com</div>Sgarman