...
- David Horwitz is taking the lead on branch management and merges for the 2.7 period, but UCT's commitment does not extend beyond the 2.7 release.
- IU does not yet have any precise commitments, but is ready to participate in a team effort. QA would be one good way to contribute. Bryan's work on the synoptic tool will likely also need his engagement.
- Michigan's resources will be focused on the set of UI changes they introduce, and for the next two years, but Gonzalo also said he's ready to help patch other UI issues in the tool as they arise.
- Clay will help in communication and documentation.
- Pete will help coordinate QA.
- Anthony will assist release management.
...
- Should have an independent release by Nov. 20.
- Gonzalo and Matt will start to merge their UI changes into trunk.
- Everyone else will review the list of changes and try to identify potentially controversial ones that would be good to highlight for the rest of the community. This will be done by Friday of this week.
- Non-controversial items will be merged directly to trunk, and the rest when the project team reaches a consensus on solutions.
- When the UI changes are merged in that snapshot will go out to a QA server for documentation and testing to begin.
- QA will need to be apprised of UI changes in order to test them effectively. Documentation on them (including screenshots) has been prepared and should be reviewed by Pete and other testers. (see Forums Interface Enhancement Feature Summary )
Next Steps:
- Potentially controversial items will be highlighted for community comment. Team members will review all issues and try to identify which need particular consideration in this way (even if the answer is 'all of them').
- Gonzalo and Matt will merge the UI changes into trunk now: due diligence has already been done to review these. Once these changes are in place a snapshot will go out to a QA server so that documentation and testing can begin.
- Pete will review documentation on UI changes and prepare for QA coordination in conversation with Megan
- Clay will renew the request for user testing from the UX group.
- When the issues have been reviewed and we have a shared (team) view of what features need broader comment, we'll begin a process of merging things in or getting broader review as the issue warrants.