Minutes from asac/fabo sync call meeting 2011-06-22

  • ACTION: kill Process/Cycle wiki page. The release process needs to be re-written from scratch based on the monthly cycles slides and the backlog management feedback.
  • ACTION: Send a reminder to PMs/TLs about:
    • - tarball/ released artifacts - headlines/highlights/changelogs/release notes - deadlines (tomorrow) - Launchpad page is preferred option (see toolchain WG as an example); if TLs/PMs dont do that we would probably want to work with them to make it happen - RISK: relies on PM as we don't have access to all Launchpad projects
      • -> if PMs/TLs dont want to do that lets get powers for them

      - in the reminder we should include which Teams we expect to deliver components - give a list of known components to ensure that people know they are on the hook
      • toolchain-4.5, toolchain-4.6, qemu-linaro, linux-linaro, linux-linaro-lt-ti, linaro-linaro-android-lt-ti, linux-linaro-lt-samsung, linux-linaro-lt-fsl, linux-linaro-lt-ste, lava (a bunch), linaro-image-tools, linaro-build-cloudd (check with james, could be skipped this month), powerdebug, powertop, compiz, nux, libjpeg-turbo?, libjpeg-turbo-android
  • compiz/nux/unity are Ubuntu components. If we continue to work on them more than a month, it could make sense to create compiz-linaro/nux-linaro projects. if they hate this, they have to do a multi tarball release against a linaro-graphics-wg project.
  • ACTION: Document this process, including announce, where to maintain milestone series we monitor etc.
    • when is deadline for releasing components
    • where to put them (here maintain a list on the wiki of the WG series we are monitoring automatically)
    • what to put in a component release (release notes, highlights, bugs, blueprints finished, tarball)
    • how to best use launchpad milestones
    • when to announce due date reminders
  • Testing should be done regularly
    • Send a reminder that we need each board tested.
    • Lack of testing on some boards will result in automated build/release removal.
    • Give removal candidates list (IGEPv2, etc...)
    • Step toward star rating system
  • Weekly testing should include info about what is the testing state of a board/hwpack:
    • hwpack is official LEB board and image (Android, Ubuntu)
    • hwpack has official sponsor (sponsors care for testing and organize bug fixing etc. - like ash for overo, landing teams for their boards)
    • hwpack has no official sponsor but got tested regularly (risk is high that testing doesnt get done and that hwpack will get killed)
    • hwpack has no official sponsor and didnt receive feedback for a while (mark the hwpack explicitly in announcement as being scheduled for removal)
    • hwpack that does not make two releases in a row due to lack of testing/bugs will be removed

Platform/2011-06-22 (last modified 2011-06-22 14:24:56)