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 what would most improve the RM process
* Knowing what's in the release ahead of time
* More recruitment of participation by early adopters
* Documentation of changes and release notes during the process
* Need to target a full release product, esp. quality documentation, and not only bug-squashing
Reviewing Proposed changes
* Need to come to an understanding of what we're facing, how it can be documented and tested.
* Will need targeted communication with team leads or individuals to elicit response
* Should be easy place for developers to see what the status of their work is, e.g. what more needs to be done
* Template for communicating the changes and what needs to be shared with the community (Scorecard and others). Too many templates right now, need a clear standard.
* Get more volunteers to review these issues other than Clay, Anthony and Pete.
* The chart lays things out as JIRA line-items, when some of them should be clumped because they may impact one another.
* Not a what should be in or out, but rather does the release team have the information it needs? Do they have test plans, documentation, etc.
- Action item: volunteers pick up "high user impact" items, and go through and document what questions need to have answers, and we'll use this small set of concrete cases to establish what our development reporting template should be.
- Megan - Forums
- Clay - Assignments
- David Haines - Synoptic tool
- Anthony - when returning work with Pete on cleaning up Jira issues
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)