[Starlingx-discuss] [build] [meetings] Build team meeting minutes 12/13/2018

Lara, Cesar cesar.lara at intel.com
Wed Dec 19 20:53:10 UTC 2018


Build team meeting 12/13/2018

Attendees
Victor, Jason, ken, Saul, Brent, Memo, Erich, Felipe, Scott, Luis, Dean, Cesar

Agenda

- ISO files retention follow up
- Overall picture for next gen build system
- Holiday schedule
- Opens
- Bug triage

Notes
ISO files retention follow up:
Unless we have some disk space issues, we keep milestones ISO files, until we retire the release that these files are part of. Once a release is out we will age out the milestone ISOs.

The proposal sent by Ken to the mailing list is as follows:
N release age out all milestones related to N-2  (N being the release)

Archive builds need to have a different discussion not necessarily with this team but at the TSC level along with the supported versions of the product

Daily ISOs will be kept for 14 days.

Overall picture for next gen build system:
There was a presentation around the implementation of a multi-OS build system by VictorR and Saul some of the highlight of that conversation were:

How do we build an image (ISO or container) needs to be the same process for any OS

The build process should start with a pile of packages and configurations that we will feed in to the build mechanism.

Direction should not be monolithic, for every distro, we start how those distros are being built, and then we figure out how we distribute those (installers, ISO, container)

Sysconfig/ kickstart setup should be abstracted from the build process, depending on the OS

We should follow a  model where we have many Git repos and tags for release and archives.

We also should take into account that what the ISO is going to shrink, there are others like the containers that will not be necessarily in the ISO. We need to consider a philosophy in which we provide  the same OS  in the host and the containers, so we avoid the support of different CVEs and packages for containers and hosts

AR Victor to break down this into multiple specs not more than one.

Holiday schedule - we will align to other sub teams and community meeting for the December break, we are cancelling our December 27th meeting and should evaluate the January 3rd 2019 one

Bug triage- all bugs for Build are properly assigned and have people working on those

Opens - no opens




Regards

Cesar Lara
Software Engineering Manager
OpenSource Technology Center

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.starlingx.io/pipermail/starlingx-discuss/attachments/20181219/654a4307/attachment-0001.html>


More information about the Starlingx-discuss mailing list