We need to start following / promoting our Juno Ramp-down plan - especially M7 exceptions Juno Rampdown plan
Some of the changes going into M6 were recently discovered by a few adopters. Changes were made to New Help for old friends post M6. Although the changes made it into M6, some adopters were caught off guard again of the nature of the breaking changes. Specifically IBM was relying on reflection techniques to resolve some differences, but the latest round has made this difficult, and changing build schemes is very hard at this point in the cycle. Can we discuss options?
Git adoption progress Continue polling - - investigate a subproject that could "pilot" a git repo feeding into our overall PDE build. - Carl or volunteer? Can start investigating building existing Git project like Libra? - More discussion on CVS - GIT transition - should replace CVS feature for feature - Tentative schedule for CVS -> Git migration post Juno (July) - Platform HAS put a stake in the ground.... CVS Retirement bug (Target: December 21, 2012)
Back to meeting list.
Please send any additions or corrections to Chuck Bridgham.
Back to the top