Difference between revisions of "VTK/SoftwareQuality/VTKDashboardHackathon1"

From KitwarePublic
< VTK
Jump to navigationJump to search
Line 22: Line 22:
 
* 15:45 - Summary reports
 
* 15:45 - Summary reports
 
** [http://review.source.kitware.com/#/q/entity:topic%20status:open+project:VTK,n,z Gerrit topics]
 
** [http://review.source.kitware.com/#/q/entity:topic%20status:open+project:VTK,n,z Gerrit topics]
** [[VTK/SoftwareQuality/GerritTestFailures|Gerrit builds]]
+
** [[VTK/SoftwareQuality/GerritTestFailures#Improve|Gerrit builds]]
** [[VTK/SoftwareQuality/ContinuousBuildTestFailures|Continuous builds]]
+
** [[VTK/SoftwareQuality/ContinuousBuildTestFailures#Improve|Continuous builds]]
** [[VTK/SoftwareQuality/NightlyExpectedBuildTestFailures|Nightly Expected builds]]
+
** [[VTK/SoftwareQuality/NightlyExpectedBuildTestFailures#Improve|Nightly Expected builds]]
 
* 16:30 - Action items
 
* 16:30 - Action items
 
* 17:00 - Adjourn
 
* 17:00 - Adjourn

Revision as of 15:15, 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

Attendees

Process

Nightly Expected builds