Core Committer Weekly Interlock - December 20th 2017

Attendees

Agenda

Sprint Release

Release 2.36.0 was made, no new content in the release although there were ~15 merges made in github.
1. Suggestion to augment the release notes to include the github messages.
2. Teams need to make sure the "affects community " field is being set correctly
Should we be making the release if no new commits?
1. team agreed to table this topic to the RackHD 2018 roadmap planning in early January.
Should we continue on with Sprint Release or move to a per merge release?
1. team agreed to table this topic to the RackHD 2018 roadmap planning in early January.

Node 6 (or 8) Status

Can Former user (Deleted) provide a status where we are with node 6 or 8 transition?
1. Functional testing for 4/6/8 in Jenkins sandbox. Next steps are to enable the default version to node 8 in dual-pipeline (concourse env).
  1. Target timeline for completion is ~ end of January 2018.
2. Suggestion to add in node 6 backwards compatibility
3. April 2018 - node 4 maintenance ends.
4. Node version 8 is the recommended version, 9 is now available.
Issue with grpc, failed with node 4. Had to lock down to specific versions as node versions are evolving….similar issues with api doc
1. https://github.com/RackHD/on-http/pull/826
2. https://github.com/RackHD/on-taskgraph/pull/351

Copyright check

Internal and external contributors and expectations on including the copyright header .
1. preliminary guidance from Tim Larson was external contributers (outside of dell emc) not required to add the copyright. Internal contributers (internal to ose org and dell emc) required to add the header. Tim was going to confirm this with legal team.
2. in the case of an external contributer with a PR missing the copyright header, the automatic copyright check but the PR can still be merged.

Review on external contributions

https://github.com/RackHD/on-tasks/pull/571 and https://github.com/RackHD/on-taskgraph/pull/346
Request on more expedient responses to feature contributions from the community - AI for all team members:)

RackHD SLack channel post from Kenny:

RackHD and Pipeline stability metrics collection over time

During the KLT meeting, it was discussed the Thomas Sullivan would create a spreadsheet in confluence that can chart the stability over time. This is for the short term.
Longer term, Felouka team is planning to support automatically generating this trend data with a target timeframe of mid- January.

Katalist Concourse Based Dashboard - to be contributed as a concourse opensource project or remain in Katalist repos?

Bishoy youssef to look in to the process of what it would take to contribute directly to Concourse

RackHD CC to Katalist CC transition

WIP, need to identify meetings charter so there will be no overlap with the 2x weekly Architecture meeting