VTK/SoftwareQuality/VTKDashboardHackathon1: Difference between revisions
From KitwarePublic
< VTK
Jump to navigationJump to search
(→Agenda) |
|||
| Line 31: | Line 31: | ||
==Process== | ==Process== | ||
[[VTK/SoftwareQuality/NightlyExpectedBuildTestFailures|Nightly Expected builds]] | |||
[[VTK/SoftwareQuality/GerritTestFailures|Gerrit builds]] | |||
[[VTK/SoftwareQuality/ContinuousBuildTestFailures|Continuous builds]] | |||
[[VTK/SoftwareQuality/NightlyExpectedBuildTestFailures|Nightly Expected builds]] | [[VTK/SoftwareQuality/NightlyExpectedBuildTestFailures|Nightly Expected builds]] | ||
Revision as of 20:16, 26 February 2013
The first VTK Dashboard Hackathon is scheduled for February 27, 2013. The purpose of this hack-a-thon is to drive the number of recurring, failing test defects to 0 on the VTK Nightly Expected dashboard.
Logistics
- Location: Kitware, Clifton Park
- Google Hangout: TBA
- Beer celebration: TBD
Agenda
Note: all times are preliminary and flexible
Location: KHQ21 Conference Room
- 9:00 - Review/modify agenda
- 9:15 - Review/modify goals
- 9:30 - Establish baseline
- 9:45 - Assignments
- 10:00 - Hack, hack, submit reviews
Location: KHQ21 Auditorium
- 11:00 - Group Gerrit Review 1
- 12:00 - Lunch
- 13:00 - Hack, hack, submit reviews
- 15:00 - Group Gerrit Review 2
- 15:45 - Summary reports
- 16:30 - Action items
- 17:00 - Adjourn
Attendees
Process
Nightly Expected builds Gerrit builds Continuous builds Nightly Expected builds
