[Toaster] Toaster Minutes 10/14/15

[Jolley, Stephen K]

Attendees: Stephen, Paul, Mihail, Elliot, Brian, Tiago, Victor, Michael, Belen, Sujith,


Updates:

Paul: Gave a demo at ELCE.

Mihail: Finished full pass for 1.8.1 QA.

Elliot: Mostly rebasing stuff while patching toaster next.  Also worked on 8320.

Brian: Not much on toaster this week. Did reply to Sujith with suggestions on how handle the Mentor use case.

Tiago: Not much on toaster last week, due to a conference and holiday.

Victor: Fixed some issues with the new theme components

Michael: Working on build info problems that occur during the command line builds. Also trying to finish up 2.0 patches.

Belen: Went to ELCE and supported dev day. Good results from dev day use of toaster.  Fixed 8449 and improved the layout of the directory structure page. Worked with everybody reviewing patches and answering questions. Worked with Elliot, Tiago and Levi to get us started in the integration of the new Toaster Bootstrap theme.

Sujith: Working on 8456.  Reviewed Brian's e-mail about layer issues.

Stephen: Working on YP and MinnowBoard project management.


Triage bugs:

https://wiki.yoctoproject.org/wiki/Bug_Triage#YP_1.9_.26_2.0_Toaster_Bugs_needing_Triage


Link to the wiki:

https://wiki.yoctoproject.org/wiki/Toaster_and_bitbake_communications


Opens:

Elliot: - Discuss if we want to backport patches/fixes to old Toaster versions?  Yes, but only major fixes and security issues.

Michael - Squashing the migrations on each major release.  For milestones migrations are OK, but at major releases no. Policy for Django from 2.1 should be only LTSs.

Michael - Starting toaster.  We have 3 methods to start it:

1.    bin/toaster (build mode),

2.    source toaster start (analysis mode) - which we have considering merging with the above

3.    production environment Toaster, with Django deployed as wsgi application with a proper web server

Do we want to keep all 3?  For YP 2.0 we can't yet combine 1 and 2. Still need to discuss and deciding what we want to do in YP 2.1, but merging the 2 modes is depending on having a stable memory resident bitbake.

Belen - Toaster next and bitbake getting out of sync, which is to be expected particularly when patches get rejected upstream. So far it looks like we should still keep toaster-next, because it provides more convenience than pain.

Belen - Bian from Fujitsu cannot join toaster calls due to timezone issues.  Should we set up an IRC channel?  Most likely not a good value. Encourage to send question to the mailing list.

Michael - 2.1 planning: should we set up a separate meeting?  Yes after some email discussion about what we want to do.


AR's:

Elliot - Comment on 8472 and recommend something regarding back porting.

Brian - Brian will email the mailing list about squashing migrations on each major release.

Brian - Ambush Michael about Patchwork. (In Process)

Brian - Check with Michael that the default assign for Toaster to a list of key contributors. (In Process)

Michael - Get details for Mentor's enhancement requests entered into Bugzilla. (#8456 - Done)

Sujith - Review Michael's enhancement requests. (Yes - Done)

Michael - Start a YP 2.1 toaster planning wiki.  Discuss in future meeting: Proposal for design of the command line builds going forward.

Stephen - Set up toaster YP 2.1 planning meeting after email/wiki discussion is done.

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 at intel.com

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/toaster/attachments/20151014/ef70246c/attachment-0001.html>