Connection Info
Telephone: +1 812 856 7060
Internet: 156.56.240.9
Sakai001
- Conference Code: 348#
- PIN: 72524#
Agenda
- Goals for the 2.7 release (insofar as release management and QA are concerned)
- First round of triage:
- which portions of work need to go to the product council
- which portions of work belong under "high user impact"
- Whether we have a branch manager, and if not what will be done to recruit one
- A discussion for how the release team should organize itself and recruit new members. (Proposal will need to be worked up to go out on-list)
- Review and Refine procedural details for next month of work
Helpful Links
Attendees
Anthony Whyte
Seth Theriault
Pete Peterson
Adam Hocek
David Haines
Steve Smail
Megan May
Charles Hedrick
Pieter Hartsook
Minutes
Overview and goals
* 2.7 out by EOY.
* During this time proposed changes to release management process will be tested, vetted and evaluated during this process.
Comments on RM process
* Knowing what's in the release ahead of time, before the release - Megan M.
* More participation by early adopters, e.g., UCT and Marist - Anthony W.
* Need for Oracle servers in the mix of QA instances - Adam H.
* Documentation of changes and release notes early on before the release date - Anthony
* How can someone fine the exact issues that are in a specific release, need to be easy list for technical and non-technical - Charles and Seth
2.7 Proposed inclusions
* Review the list of proposed items and evaluate the value and QA impact of each
* Are we catching the all the needs?
* Focus on the team leads or individuals for projects and developers to illicit response
* Should be easy place for developers to see what is going in the release
* Template for communicating the changes and what need to shared with the community (Scorecard and others). Need a standard template.
* Get more volunteers to review these issues other than Clay, Anthony and Pete.
* Group related items
* Focus on what the template should look like
* Not a what should be in or out, but rather are the proposals ready to be included. Do they have test plans, documentation, etc.
* Focus on the questions/forms needed to ask for each proposal - Megan
Release Team Creation
* Release team organization is being organized right now
* Branch manager volunteers - David and Stephen? Need more branch managers for this effort.
* What is the process for putting together the release team? Anthony - Work with group of interested people who are able to commit and work on reviewing jiras, etc. More community engagement in this process.
* Harmonizing Sakai community on the overall release
* Page in confluence that summarizes branch managers and other roles and who or whom is the contact for them. - Anthony
* Idea: color code release status (green, yellow, red, etc)
Next Steps
* Megan - Forums
* Clay - Assignments
* Michigan - Synoptic tool
* Anthony - when returning work with Pete on cleaning up Jira issues