Core Commiter Weekly Interlock - January 23rd,2017

Former user (Deleted)

Jeanne Ohren

Andrew Hou

Geoffrey Reid

Amy Mullins

Brian Parry

Paul Scharlach

Leo Zhang

Rahman Muhammad

Thomas Sullivan

Agenda:

1. Timing of meeting - last couple of weeks we have gone over on the dev scrum meeting should we move this by 15-30 min?
   1. AI Thomas Sullivan to work on dev scrum meeting efficiency.

1. 1.0.0 Release

This Friday is end of sprint we need to determine new version number.   1.1.0? or 1.0.1?   The release this Friday is 1.1.0.

Final approval will be on Wed after release at OLT if something looks "fishy".   If it is a slam dunk with the release on Monday we can release on Monday.    We will discuss at Core Committer on Monday meetings on whether it should go in front of OLT for approval if there are issues.

• RI-45 will this require a minor or major bump?  Event notification change https://rackhd.atlassian.net/browse/RI-45  
• Public API is just Rest API.   Should not include data model in public facing API and thus no need to bump major version.   We should make any upgrade to data model transparent to the users.
• AI Former user (Deleted) to send email about data model changes to google groups.

• Process - how do we communicate to public?
  • Slack? pin an announcement on slack (need to check on this tool AI Thomas Sullivan
  • On rackhd landing page?  put a link to latest version on the webpage. AI Thomas Sullivan
  • create a DL for open source to subscribe to?
  • Google groups? AI Thomas Sullivan
  • Twitter? No
• How many older releases do we need to keep (YTJohn issue - where we deleted older labels that he was depending on)  There is a limit due to cost of hosting more images.   Do we put this issue on the customer to maintain the version they have  "pinned" to.   Need to figure out how to communicate to the public our process so they can watch for releases to disappear and act accordingly.  AI Thomas Sullivan -figure out cost/sizing issue to store additional releases.
• How do we want to handle the bugs created by the QRB team
• Who triages and assigns the bugs?  AI - Former user (Deleted)  UPDATE: Talked with Amy.  For now the QRB team will make best guess at triage.
• Special meeting - or email
• Current issues
  • https://rackhd.atlassian.net/browse/RAC-4004   - AI Leo Zhang to talk with Former user (Deleted) about opening new bugs when a new build fails.   Can we release if there are missing deliverables?
  • https://rackhd.atlassian.net/browse/RAC-4034 - already done
  • https://rackhd.atlassian.net/browse/RAC-4035 - AI Former user (Deleted) to work with Amy Mullins if this is owned by her team.  UPDATE assigned this to Amy.
• Who follows Peter Pan's recipe on Friday to make this new label?
• Paul Scharlach to pony up a resource to kick of the official build of 1.1.0 on Monday Jan 30th
• How to Do Sprint Release[deprecated] 

1. Vagrant Box issue - lots of emails where do we sit on this. Build special vagrant box for the community Former user (Deleted) submitted as submitted a PR 588 - customer to be able to download the source to a bare vagrant box.   
2. Pending PR Reviews
   1. https://github.com/RackHD/on-http/pull/554 - need Brian Parry need to review for Leo and Krein ASAP as Chinese New Year is upon us - AI - Former user (Deleted) to follow up with Brian Parry  UPDATE Former user (Deleted) is looking at this PR.
3. AI Paul Scharlach to talk to Roland about on-taskgraph container build failures in dockerhub did this happen? Roland is looking into failures.   UPDATE: On-taskgraph containers is now passing.
4. Roundtable