Attendees: Elliot, Stephen, Paul, Mihail, Ed, Brian, Tiago, Victor, Sujith, Alex, Belén, Michael,
David Updates: Elliot: Working on 8417 this week. Finished 8373. Paul: Not much on Toaster work Mihail: Working on full pass of YP 2.0 rc3. Ed: Not much on Toaster work, but some work on 8279. Brian: Not much work on Toaster Tiago: Work on test plan with Belen and work flow. Victor: Working on build expert screen. Sujith: Not much Toaster work. Alex: Working to develop YP 2.1 toaster testing plan. Belén : Working with Elliot on the bug 8417. Michael: Working on image customization. David: Not much with Toaster Stephen: Working on YP project management. Triage bugs:https://wiki.yoctoproject.org/wiki/Bug_Triage#YP_Toaster_Bugs_needing_Triage Link to the wiki: https://wiki.yoctoproject.org/wiki/Toaster_and_bitbake_communications Opens: Belén - Planning for YP 2.1 toaster improvements - Push to discuss next week. Belén - lsupdates command. Updating the information might override layer data from builds, which is more up to date than the layer index. The main reason you want to run lsupdates is if new layers are posted in the layer index. We need to keep lsupdates, but we need to have good enough version management so that recipe entries are not duplicated. Paul's solution is local data from builds masking data coming from the layer index. Brian would like to see some real world examples of the data conflicts between build and layer index data. To recreate the problem you just need to run a build and then run lsupdates. Brian needs to understand this better, so we'll give him an AR, but we all agree that it would be a pity to prevent users from updating the data from the layer index. Belén - Image customization - We discussed where recipe information packages come from. We all agree that custom images should show the proper recipe generating the packages, instead of showing the name of the custom image. But we don't actually know how to do it, so we need to discuss the changes that need to be made for this. Belén - handling packages generated that are not explicitly listed in the metadata. There is a very small set of packages that are produced by a build that are not explicitly listed in any recipes (glibc locale packages aren't meant to be individually selected: they are determined by your locale selections). According to Paul, the list of packages shown to users should be everything in IMAGE_INSTALL from the base recipe, plus / minus the packages the user added / removed. We should also display package groups. We should keep a full list (an implicit list stored in the database) to keep an accurate picture of the outcome of the build. The explicit list (the one shown to users in the UI) should be made of the ones in IMAGE_INSTALL plus the packages the user added / removed. We should schedule a separate discussion to nail down the implementation details. AR's: Brian - Brian will email the mailing list about squashing migrations on each major release. (In Process) 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) Mihail- Review patch for selenium test. Belén - compile a list of the planning items sent to the mailing list so that they are easier to discuss next week. Brian - Do an investigation of lsupdates command and possible conflicts. Belén - schedule an additional meeting to finish off the discussion about how to generate the package list for custom images and how to show the proper recipe information for packages in custom images. Brian - Talk to Jessica about image customization issues. 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: [email protected]
-- _______________________________________________ toaster mailing list [email protected] https://lists.yoctoproject.org/listinfo/toaster
