VTK/ARB/Meetings/January 2011: Difference between revisions
From KitwarePublic
Jump to navigationJump to search
(Created page with "== Agenda == * Review action items from last time ** Send any additional multi-threading use cases to Stephane. ** Coordinate on setting up "modules" for VTK Journal (Bill and Wi...") |
No edit summary |
||
| (2 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
== Time == | |||
January 18th, 1pm EDT | |||
== Agenda == | == Agenda == | ||
* Review action items from last time | * Review action items from last time | ||
| Line 6: | Line 9: | ||
* VTK reorganization update | * VTK reorganization update | ||
* VTK workflow (Berk) | * VTK workflow (Berk) | ||
** ITK experiences with [http://review.source.kitware.com/#q,status:open,n,z Gerrit] | |||
== Meeting Notes == | == Meeting Notes == | ||
* Release | |||
** Finishing VTK dashboard cleanup, release soon | |||
** New charting classes, widget tweaks | |||
** Migrate changes from Slicer to VTK master | |||
* Reorganization | |||
** Waiting until Feb. | |||
** Marcus Hanwell will do majority of reorg | |||
** Berk will work on separating algorithms from pipeline, changing behavior of SetInput() to not make a pipeline connection | |||
** There may be additional changes needed to the filter internals when this change happens | |||
* VTK workflow | |||
** More formal procedures needed for developing VTK, as in documentation | |||
** Consider using gerrit for code review | |||
** Run only tests that are impacted by a change | |||
** Do we need master/next if we have gerrit? | |||
** Caution against getting too formalized, you will have less involvement | |||
== Action Items == | == Action Items == | ||
== Next Time == | == Next Time == | ||
* More about workflow | |||
Latest revision as of 19:08, 18 January 2011
Time
January 18th, 1pm EDT
Agenda
- Review action items from last time
- Send any additional multi-threading use cases to Stephane.
- Coordinate on setting up "modules" for VTK Journal (Bill and Will).
- VTK release update
- VTK reorganization update
- VTK workflow (Berk)
- ITK experiences with Gerrit
Meeting Notes
- Release
- Finishing VTK dashboard cleanup, release soon
- New charting classes, widget tweaks
- Migrate changes from Slicer to VTK master
- Reorganization
- Waiting until Feb.
- Marcus Hanwell will do majority of reorg
- Berk will work on separating algorithms from pipeline, changing behavior of SetInput() to not make a pipeline connection
- There may be additional changes needed to the filter internals when this change happens
- VTK workflow
- More formal procedures needed for developing VTK, as in documentation
- Consider using gerrit for code review
- Run only tests that are impacted by a change
- Do we need master/next if we have gerrit?
- Caution against getting too formalized, you will have less involvement
Action Items
Next Time
- More about workflow
