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

From KitwarePublic
< ITK‎ | Tcons‎ | Agendas
Jump to navigationJump to search
Line 23: Line 23:
* http://www.itk.org/Wiki/ITK/Release_Schedule
* http://www.itk.org/Wiki/ITK/Release_Schedule
===ITK-v4.2===
===ITK-v4.2===
June 2012
 
All New Code should be in Gerrit by May 21th, preferable before, to allow time to review and revise.
* June 2012
Reviewers should plan time to review this week
* All New Code should be in Gerrit by May 21th, preferable before, to allow time to review and revise.
Feature Freeze May 28, 2012
** Reviewers should plan time to review this week
Weekly Release candidates only to address bug and clean dashboard
* Feature Freeze May 28, 2012
ITKv4.2.0rc1 June 1st, 2012
* Weekly Release candidates only to address bug and clean dashboard
ITKv4.2.0rc2 June 15st, 2012
** ITKv4.2.0rc1 June 1st, 2012
ITKv4.2.0rc3 June 22nd, 2012
** ITKv4.2.0rc2 June 15st, 2012
* ITKv4.2.0 release June 30th, 2012
** ITKv4.2.0rc3 June 22nd, 2012
'''* ITKv4.2.0 release'''  June 30th, 2012


== Dashboard ==
== Dashboard ==

Revision as of 13:51, 27 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

Release Schedule

ITK-v4.2

  • June 2012
  • All New Code should be in Gerrit by May 21th, preferable before, to allow time to review and revise.
    • Reviewers should plan time to review this week
  • Feature Freeze May 28, 2012
  • Weekly Release candidates only to address bug and clean dashboard
    • ITKv4.2.0rc1 June 1st, 2012
    • ITKv4.2.0rc2 June 15st, 2012
    • ITKv4.2.0rc3 June 22nd, 2012

* ITKv4.2.0 release June 30th, 2012

Dashboard

Gerrit

  • Any that needs discussion?

Other Isssues

Review JIRA

  • JIRA is down
  • 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

1