From: Michael Wood <michael.g.wood@intel.com>
To: toaster@yoctoproject.org
Subject: Re: Toaster Weekly Meeting Minutes 03/30/16
Date: Wed, 30 Mar 2016 20:47:17 +0100 [thread overview]
Message-ID: <56FC2D45.9060506@intel.com> (raw)
In-Reply-To: <9ADD3FDE8B189B4AA2F8A3C711F8155E5709BBE1@fmsmsx111.amr.corp.intel.com>
Just updated a wiki page which contains a bit more of an overview of
Toaster as I don't think we have anything high level at the moment.
Could do with more detail but hopefully others can also add to it.
https://wiki.yoctoproject.org/wiki/Toaster_architecture_design
On 30/03/16 16:43, Jolley, Stephen K wrote:
>
> *Attendees:*Elliot, Stephen, Michael, Mihail, Ed, Joshua, Dave, Belen,
> Sujith, David, Brian, Daniel,
>
> *Updates:*
>
> Elliot: Submitted upstream Dave’s patches. Finished 9011 and 8511.
>
> Michael: Reviewing porting of self tests to unit tests.
>
> Mihail: Finished automating the manual tests for Toaster. Should be
> pushed next week. M3 rc2 testing is in process.
>
> Ed: Working on 7880. 7th version of patch in review.
>
> Joshua: Working to reproduce 9115 and can’t. Problem might have been
> resolved.
>
> Dave: Reviewed 9163. Working on 9137.
>
> Belen: On vacation. Preparing for ELC dev day. Reviewing Ed’s patch.
>
> Sujith: Pushed changes for 7225.
>
> David: Mostly working ELC items. Working on 8037.
>
> Brian: Mostly working on ELC and checking branches for review.
>
> Daniel: New to Toaster. Reviewing 8328.
>
> *Triage bugs:*
>
> https://wiki.yoctoproject.org/wiki/Bug_Triage#YP_Toaster_and_Layer_Index_Bugs_needing_Triage
>
> Link to the wiki:
>
> https://wiki.yoctoproject.org/wiki/Toaster
>
> https://wiki.yoctoproject.org/wiki/Contribute_to_Toaster
>
> https://wiki.yoctoproject.org/wiki/Toaster_and_bitbake_communications
>
> *AR’s: *
>
> Michael - Expand documentation on image customization (Done)
>
> Brian: Discuss with RP timing on fix for Toaster starting up. (Done)
>
> *Opens:*
>
> Michael - Unit testing are ready to be submitted. They are based unit
> tests in Django unit test. A number of patches (44?) are in Ed’s
> branch and are needed to make this happen right. We need to test
> these and submit them for M4.
>
> Belen - Which branch should we use for Dev Day? Master-toaster-next?
> Make a copy of toaster next and insure it is stable and then keep it
> stable.
>
> Daniel - Suggestions on how to help. Review the Wiki links above. Ask
> questions on the mailing lists or IRC.
>
> Thanks,
>
> */Stephen K. Jolley/**//*
>
> *Yocto Project Program Manager*
>
> *INTEL, MS JF1-255, 2111 N.E. 25th Avenue, Hillsboro, OR 97124 *
>
> (*Work Telephone*: (503) 712-0534
>
> (*Cell*: (208) 244-4460
>
> * *Email*:_stephen.k.jolley@intel.com_
>
>
>
prev parent reply other threads:[~2016-03-30 19:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-30 15:43 Toaster Weekly Meeting Minutes 03/30/16 Jolley, Stephen K
2016-03-30 19:47 ` Michael Wood [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=56FC2D45.9060506@intel.com \
--to=michael.g.wood@intel.com \
--cc=toaster@yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.