Option A: Release instrument and instrument manager ASAP
+ Code is kept clean
- We have alot to do
Option B: Make dependencies on instrument soft by using
reflection.
+ We can take our time with instrument
- Reflection code is ugly. Deciding factors:
* Are the interfaces something we like? If so +1 on release
* How much work is involved in bringing it close enough
for release? If too much -1.
* Are we comfortable with the reflection based approach
to loosen the requirement for Instrument?
* At a minimum Instrument and Instrument Manager need
to be released.Step two: Prepare all ECM depenedencies (and ECM/TestCase)
for release. * All fully deprecated packages (like concurrent and
collections) get moved into a "compat" project that
exists strictly to provide a backwards compatibility
layer. The original location gets nuked.Step three: Prepare all Fortress dependencies (and Fortress/XFC)
for release.* Decide if we want to deprecate Pool (only used in ECM)
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
