ITK/Release 4/DICOM/Tcon 2011 05 20: Difference between revisions

Revision as of 05:14, 20 May 2011

our fork of ITK is now stable, we keep the GDCM warnings ON in our copy time to address them. then we will switch main ITK back on.
building our branch of itk against linux, mac and windows:
- < drew put the name of the machines on the dashboard here >
- < each meeting should start or include browsing those machines and discuss remaining bugs/warnings >

update patches on gerrit from github (including brad K patch), merge those in ITK
- note for the community, it is possible that all third party module fail teh same way when using system versions ...)
Iron out all remaining warnings / failing tests with systems gdcm
merge system gdcm in ITK on github (to have gdcm warnings enable on our buildhosts)
Iron out new errors / warnings if any
Merge in ITK (ouch - help?)
re-enable GDCM errors in ITK
redirect our buidlhost to main ITK

@@ Line 9: / Line 9: @@
 ** < each meeting should start or include browsing those machines and discuss remaining bugs/warnings >
-== next week ==
+== next week (and more) ==
-* stabilize build hosts
-* WIn 7 testing and stablization
-* update patch on gerrit, merge
-* re-enable GDCM errors in ITK (or at least in our fork of ITK) in repository
-* Resume merging of gdcm in ITK
-** by cherry picking the good fixes from mark/drew that are kept in the GDCM21Merge branch of our repository
+* update patches on gerrit from github (including brad K patch), merge those in ITK
+** note for the community, it is possible that all third party module fail teh same way when using system versions ...)
+* Iron out all remaining warnings / failing tests with systems gdcm
+* merge system gdcm in ITK on github (to have gdcm warnings enable on our buildhosts)
+* Iron out new errors / warnings if any
+* Merge in ITK (ouch - help?)
+* re-enable GDCM errors in ITK
+* redirect our buidlhost to main ITK
 == Before June meeting ==