Hi all, Yesterday, we had a discussion on the Upstream-Process for the ADB Ecosystem. The issues discussed and the resulting action items are listed below.
For the detailed discussion - https://etherpad.openstack.org/p/upstreamprocess *Release Process:* - Fix and communicate Code freeze dates within the team as well as to the QE. - Co-ordinate with QE team to do end to end testing for sanity every week (devsuite, devstudio on Windows and so on); maybe every Wednesday or Thursday. So that the Dev team would know if there are any blockers by every Monday. This needs to be discussed and confirmed with the QE team - Testing, sanity checking needs to be done by developers too before going to QE *Release Cycles:* 3 week release cycle finalized - Every 3rd Thursday - 3 weeks release cycle seems optimal as it helps get in more features, and is in alignment with the sprint. - If sprint ends on Tue; ADB utils needs to be released the Friday before it. All the other components (ADB, VSM etc) should be released together the Monday before. - QE will get it on the same day (Monday) and test simultaneously. QE needs to do an end to end, sanity check each week and highlight blockers if any. *Review process:* - Identify 2 PR-buddies for each week; whose focus for the relevant time period is to troubleshoot/resolve all PRs in the project repo, connect the relevant people, direct the PR to the respective maintainers. This will help in quick PR reviews and quick integration, ideally PR-Review should start the same day. This week Lala and Budhram have volunteered for this. - For documentation/code feature, start the work on a local feature branch, discuss in the GitHub issue or in the developer feature branch fork and send the PR when the first draft is ready. Discussion should happen before the PR, and not on the PR. - Milestones must be set for every 3 weeks and mentioned in the Git hub, so that it is in sync with the Sprint cycle and makes the priority features obvious. Regards, Preeti
_______________________________________________ Container-tools mailing list [email protected] https://www.redhat.com/mailman/listinfo/container-tools
