Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

Participants

  • Megan May
  • Bryan Holladay
  • David Haines
  • Gonzalo Silverio
  • David Horwitz
  • Pete Peterson
  • Anthony Whyte

Notes

Players and Roles:

  • 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, 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.

Set of Changes:

  • Michigan's UI changes have been documented and published for some time, and were also reviewed earlier in discussion with IU. Suggested changes were made. It's ready to be merged into trunk.
  • David has prepared a branch from Capetown's msub patches, but there are others in a google spreadsheet. These all need to be reviewed. Clay will pull these all together into a single list
  • Daphne may also still be willing to help out with user testing.

Logistics:

  • 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 )
  • No labels