...
* 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, before the release - Megan M.
* More recruitment of 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 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 is going in the releasethe status of their work is, e.g. what more needs to be done
* Template for communicating the changes and what need needs to be shared with the community (Scorecard and others). Need a standard templateToo many templates right now, need a clear standard.
* Get more volunteers to review these issues other than Clay, Anthony and Pete.
* Group related items
* Focus on what the template should look likeThe 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 are the proposals ready to be included. does the release team have the information it needs? Do they have test plans, documentation, etc. * Focus on the questions/forms needed to ask for each proposal - Megan
- 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)
Next Steps
...