ITK/Tcons/Agendas/2012 04 20: Difference between revisions

From KitwarePublic
< ITK‎ | Tcons‎ | Agendas
Jump to navigationJump to search
(Created page with "= How to Join the Tcon = == Number to Call == '''Please be patient, due to some unforeseen circumstances, the call may not start on time...''' * 1-800-728-9607 (in the US) or...")
 
 
(4 intermediate revisions by 2 users not shown)
Line 21: Line 21:
** http://www.itk.org/pipermail/insight-users/2012-April/044437.html
** http://www.itk.org/pipermail/insight-users/2012-April/044437.html
* http://www.itk.org/Wiki/ITK_Release_4/ReleaseSchedules#Plan
* http://www.itk.org/Wiki/ITK_Release_4/ReleaseSchedules#Plan
* http://www.itk.org/Wiki/ITK/Release_Schedule


== Dashboard ==
== Dashboard ==


* http://public.kitware.com/dashboard.php?name=Insight
* http://public.kitware.com/dashboard.php?name=Insight
* NEW Visual Studio 10 Debug Build With Testing and Examples
** http://open.cdash.org/buildSummary.php?buildid=2203519
** Many FastMarching filters are timing out!
** Three InterpolateImageFunctions are failing with way off values!
==Gerrit==
* Any that needs discussion?
** http://review.source.kitware.com/#/c/5275/  Add remote module support.


== Other Isssues ==
== Other Isssues ==
Line 32: Line 43:


==Goal==
==Goal==
* Address the large number of out standing ticket that was schedule for 20120321_SpringMilestone
* Specifically look through bugs that are critical and should be promptly address.
** Move unattended tickets and issue to Derelict status
* Discuss policy on meaning of  Priority. Should a certain priority indicate that a patch should be applied to the release branch? Should a certain level of priority always be addressed before the next release?
* Review issue for next sprint to end May 5th
** Blocker
** Critical
** Major

Latest revision as of 18:13, 20 April 2012

How to Join the Tcon

Number to Call

Please be patient, due to some unforeseen circumstances, the call may not start on time...

  • 1-800-728-9607 (in the US) or
  • +1 9139049873 (international)
  • access code 6815251

Webex

Status [ Quick 10 Minutes]

Release Schedule

Dashboard

Gerrit

  • Any that needs discussion?

Other Isssues

Review JIRA

  • issues.itk.org

Goal

  • Specifically look through bugs that are critical and should be promptly address.
  • Discuss policy on meaning of Priority. Should a certain priority indicate that a patch should be applied to the release branch? Should a certain level of priority always be addressed before the next release?
    • Blocker
    • Critical
    • Major