Attendees
Agenda
Sprint Release
- Release 2.36.0 was made, no new content in the release although there were ~15 merges made in github.
- Suggestion to augment the release notes to include the github messages.
- Teams need to make sure the "affects community " field is being set correctly
- Should we be making the release if no new content
- commits?
- 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?
- 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?
- 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).
- Target timeline for completion is ~ end of January 2018.
- Suggestion to add in node 6 backwards compatibility
- April 2018 - node 4 maintenance ends.
- Node version 8 is the recommended version, 9 is now available.
- 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).
- Issue with grpc, failed with node 4. Had to lock down to specific versions as node versions are evolving….similar issues with api doc
...
- Internal and external contributors and expectations on including the copyright header .
- 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.
- 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:
- Status update update - still a WIP on if they will remain in the code repos or move to the rackhd repos
https://github.com/codedellemc/docker-machine-rackhd
https://github.com/codedellemc/gorackhd-redfish
https://github.com/codedellemc/gorackhd
https://github.com/codedellemc/rackhdcli
...
- During the KLT meeting, it was discussed the Thomas Sullivan would create a spreadsheet in confluence that can chart the stability over time. Is this agreeable to the team?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