Core Commiter Weekly Interlock - January 30th,2017
Agenda:
- Timing of meeting - last couple of weeks we have gone over on the dev scrum meeting should we move this by 15-30 min?
- AI Thomas Sullivan to work on dev scrum meeting efficiency.
1.1.0 Release - we have a candidate few open issues
http://rackhdci.lss.emc.com/view/BuildRelease/job/BuildRelease/job/BuildRelease/202/
http://rackhdci.lss.emc.com/job/SprintTag/ has a couple of failures.
AI Former user (Deleted) could we just push the end of sprint vagrant to Atlas this is fro Rac 4085
AI Tim Larson do we really need to push every night to Atlas, or can users just use the Vagrant box from the sprint end release?
P1:
https://rackhd.atlassian.net/browse/RAC-4004 - need to stabilize the build , suggestion to close this RAC and open one-off issues as they arise.
https://rackhd.atlassian.net/browse/RAC-4053 - doesn’t appear to be an issue any longer
https://rackhd.atlassian.net/browse/RAC-4055 - Between Jeanne and Peter, RAC issue is resolved. Additional issues arose during debug and tracked:
https://rackhd.atlassian.net/browse/RAC-4083 (p2) AI Former user (Deleted) can this be closed now? Appears to be resolved
https://rackhd.atlassian.net/browse/RAC-4085 (p3)
https://rackhd.atlassian.net/browse/RAC-4084 (p2) AI Former user (Deleted) working with Atlas to figure out why release flag is not on the release.
P2:
https://rackhd.atlassian.net/browse/RAC-4034 - WIP, Jeanne’s comments discussed in QRB meeting last week. RAC issue can stay P2 and I’ll send out details on this.
AI Tom Capirchio do we want to pre-install SKU packs? See Peter Pan questions in Rac4034 1) in sku pack, will the debian packages being used ? CC need to make the call. if yes. both FIT/Travis/Jenkins need to take action to build them. 3) do we need SKU Pack pre-installed in released ova/vagrant/docker? ( this is another story OSE need to consider) Should we be building Debian packages at all?
UPDATE: Per TomC "we said no to having ski packs built into ova. It will create unnecessary bloat. A consumer would include the necessary skupacks to their environment"
Will update the RAC item as well
https://rackhd.atlassian.net/browse/RAC-4035 – Still an issue. In a parallel effort, the Gripen team looking in to expediting adding regression test as a PR quality gate. Looking to add resource pools for parallel testing today.
Do we go forward with the actual release? Jeanne to do this again this week
AI Former user (Deleted) Thomas Sullivan go through bugs and determine which bugs affect community and to talk about the triage process for open bugs. How do we triage? Who assigns the priority and owner? Do they originally get assigned to the unknown backlog and then get assigned to a specific group backlog? Also how many items are not in a group's backlog (i.e. in the unassigned backlog?)
Ship it 1.1.0 - all team members agree that 1.1.0 can be released. AI Former user (Deleted) to build official candidate of 1.1.0
AI All dev managers to go through list of open PR's and see if old ones can be closed out. Need to email submitter to see if they want to pursue the PR if no answer by 1 week then the PR will be automatically closed
AI Former user (Deleted) to work with Mustang team to get any generic bug fixes for RackHD that affect the mustang collateral - need to open up JIRA ticket and submit PR for the changes that are generic to RackHD.
AI Thomas Sullivan to figure out how we shutdown Github issue creating and force users to use JIRA. Is there away to disable creating of github issue and have a redirect to JIRA?
- Brian Parry how are we doing for the new data model change? Any issue for customers? This change did not go into the release.
- GitHub issue 602/ https://rackhd.atlassian.net/browse/RAC-4088 default RackHD BMC not being created
- Open Issues from Peter Pan/ytjohn
- Round Table