Meeting: Lead call 1on1

  • Participants: asac, slangasek

  • Topics: Devplatform service for WGs, PPAs, Tools/Toolchain PPA, Images, Rebuilds, Multiarch

Minutes

  • PPAs:
    • what does dev plaform offer
      • release integration into ubuntu and official PPAs
      • component releases and continuous integration (packages) are opt-in for WGs
      • for component and continuous: initial packaging or packaging changes would be done as service by developer platform
      • updates would be straight forward and offer a script; continuous integration could be done by bot
      • uupdate and bzr versioning should handle the versions properly for them
      • sum up: we start with monthly component and daily ppas having write access to WGs
        • for that create a WG-maintainers team so approving folks there is at discretion of WG tech lead
        • to ensure that Platform/DevPlatform can properly support this, linaro-maintainers must be member of each team

        • review end of 11.05 if component PPAs or even daily PPAs should be write only by linaro-maintainers
      • all-mix PPA:
        • writable by linaro-maintainers
        • cherry pick components from WG ppas
        • good for more-continuous integration; content here should flow into automated validation farm
        • based on the development release
    • how to provide dev platform packages for component releases
      • problem: in ppa the debs might disappear, so previous compnent releases might not have the debs anymore
      • however, latest component release is always availbale at this ppa
      • for now release should just say: for your convenience the most recent componetns are also available in a ppa
  • tools/toolchain PPA:
    • should this be merged? ACTION: steve to think about it.
    • need backports and high quality/stability because its a host tool
    • steve not sure if marcin should upload there directly; toolchain ppa could serve as staging ppa and steve to review and copy to "official" tools ppa
    • you enable the tools ppa if you want to work with the latest linaro images
    • asac wants tools ppa to continue working on what it worked for before; meaning: basically needs to work for everything
    • we can however, define support cycle; but last LTS on host should always be supported
    • in other words: yes, primary goal is to enable developers to work on the current development release of linaro
    • however, things shouldnt break for the stuff you started working on with this just through dist-upgrade your host
    • goal: try to get to a point where developers can be confortable to stay on tools ppa and still use old linaro releases

    • linaro-image-tools baking
      • bake in ubuntu development release milestoned
      • smoke testing by developer platform should be done
        • not all images need to be tested
      • infrastructure uploads on their own
        • special case because they are part of platform and have dev team
        • developer platform should be responsible for uploads to ubuntu and tools ppa in general
        • upload to ubuntu development release
        • wait a week; evaluate bugs; do smoke testing against backports and deve release; upload to PPA
        • steve can make exceptions to process at his discretion; fast pathed if there is a really bad bug
        • cross-compiler backports: staging PPA: for now use toolchain PPA as that; rename later
  • Images
    • nano image: as small as possible and a shell -> busybox

      • rootfs or initrd?
      • steve to go back and think about
    • developer image (size) :
      • package list was defined at UDS
      • image: powermanagement WG tools + tracing tools (strace,oprofile etc.), lttng (currently not in the kernel), debugger, editor, sshd running by default; gdb-server goes everywhere; toolchain developer image; build-essential
      • could work as a arm sysroot; but multiarch is the cross goal
      • some tricks for size reduction
    • alip image: small + cross compilable
      • cross compiling support into the packages is ongoing; not all upstreamable
      • problems with packages that automatically get pulled into the ARM images
      • what about the future; can we have packages not-installed that are essential;
      • missing: tool to identify clustering
    • Ubuntu Evaluation Build: reuse the ubuntu seeds -> Ubuntu Evaluation Build

      • compliance/trademark constraints (canonical wont give special exception)
      • steve to review the trademark policy; and think about a name
    • multimedia/graphics it was convenience images
      • can stay; but not released
      • if they want it we can continue
      • asac feels semi-strong about keeping them because he wants to work on improving how those images support WGs
  • rebuilds/cross-compile
    • xdeb for cross-compiling
    • sbuild for native building
    • ppearse started to submit to the ubuntu archivew
    • xdeb multiarch implementation needs to be implemented
  • multiarch:
    • raffael is works for linaro till end of february on this
    • asac pointed out that we should try to encourage him to also join #linaro

Platform/2011-01-26 (last modified 2011-01-31 22:18:25)