Greetings All, Links to the RDO-CI team scrum[1] and recording[2] from this week's meeting are below. Highlights: - Document how to get involved with TripleO CI Squad: Documents proposed: - Deploying with, and debugging tripleo-quickstart - How to add and review patches (for example: adding the bug number to review for workarounds) - Best practices and coding standards (similar to what was used in khaleesi) - RFE to collect tips, information, request for the documentation [3] - Adopt a standard template for RFEs for tripleo-quickstart - See example: https://bugs.launchpad.net/tripleo-quickstart/+bug/1657191 - Sections to be included: - Background/Motivation - Proposed change - Desired outcome - Open questions/Considerations - Replace the use of tags within quickstart - See [4] - rasca will add a review to continue the discussion next week - replace tags with 'when: ... |boolean' or use a 'workflow' config - Support/liason for the Lifecycle team - Lifecycle team CI would like to use tripleo-quickstart for tests on backwards compatibility and upgrades - Requesting focused support for this work over the Ocata cycle - Demo of gertty [5] [1] - https://review.rdoproject.org/etherpad/p/rdo-infra-scrum [2] - https://bluejeans.com/s/8fREs/ [3] - https://bugs.launchpad.net/tripleo-quickstart/+bug/1659088 [4] - https://trello.com/c/k4ZOZ7hX/545-create-rfe-bug-and-mailing-list-thread-... [5] - https://gist.github.com/adarazs/6af4d26fbb9e3d3350e756d818468f8a#file-how... /R Ronelle Landy