Attendees: Matt, Vincent, Daisy, Raymond, rtripath, Dave Grove, Olivier, Duy, Tyson, Dan, Glynn, James Thomas, Dragos, Carlos, Nilly, whisker, 
Notes:
  • Matt Rutkowski moderating
  • last meeting was 2018–12-08
Introductions of new attendees
  • Dan McWeeney, Adobe… logging / Mesos integration
  • Felix Meschberger is stepping down as mentor to be replaced by Bertrand Delacretaz <bdelacretaz@apache.org>
  • TBD
Open comments on status 
Topics / agenda items
  •     Graduation / Release Mgmt. (VIncent)
    • https://cwiki.apache.org/confluence/display/OPENWHISK/OpenWhisk+Release+Process
    • Use the repo: https://github.com/apache/incubator-openwhisk-release
      • to coordinate cross-repo builds / signing / release
    • RAT on tarballs/zips
    • Dragos: creating release from ind. repos as well?
    • Vincent: central mgmt. goal is 1 major release for each repo.?
    • Carlos: once we release/name version/and hash, we go across all repos and tag each
      • doing voting  release / distribute done we can tag; use hashes initially
    • Dragos: cross-link to the release repo. …
    • Tyson: is there some rule about releasing “all at once”? 
      • the process described an uber release of all the repos.
      • some other projs. have releases ind. of other repos.
    • Matt: like Cordova, start with “core” and have satellite / follow-on releases, etc. need contribs. to help and build from there
    • Carlos: “it's a journey”, for now start with set of core repos; other repos, may be behind that for example.
      • let’s do it on a way best for maintainers (not for users)
    • Dan (chat): shared this link https://github.com/apache/carbondata/releases
    • Dan: why use submodules?  seems odd…
    • Carlos: do it in directories? do it in one uber dir? choices…
      • ideally have one versioned folder they can click on… instead of chasing tags. more consumable
    • Dan: Use github releases, can see tag in that repo.
    • Carlos: tag the (release ) repo. which will kickoff a release
    • Carlos: if we can do submodules we can try it like that
      • do modules for now instead of copying whole thing.
  • Mesos:
    • Mesosphere
    • Dragos: plan to offer community packages
      • plan to kickoff internal release then focus on community versions
      • Tyson can keep us honest, but first few months / quarter… looking to publish install scripts to have one command to deploy everything into a Mesos cluster
    • Tyson: similar to Kube, we have 2 tracks
      • “openwhisk classic” in DCOS (mainly a depl. excer.)
      • other in Mesos container factory, use instead of Docker CLI in Mesos cluster
      • Dave had an issue created to describe 2 approaches
      • Config changes, not huge, around controller and invoker IDs
        • similar need for controller to have dynamic IDs (for mult. controller configs)
      • SPI impls. in master things are simple, but in real world (outside master codebase) not anything good to help “build” them in a repo.
        • for release process, need Java JAR artifacts built as part of the release process to make some of these things ealier and providing docs
        • convention for building your custom images with these JARs… to enable other plug ins
  • CRON (Travis nightly builds)
Confirm moderator for next call (i.e., Wed. Nov 8th)
  • Dragos volunteers. for Jan 17th meeting
  • No labels