Noel J. Bergman wrote:
Berin,
We are getting away from supporting those projects, and they have
reasonable replacements (most of them any way). The compatibility
project is used to provide a holding place for all projects we
are no longer actively supporting--so that users have time to migrate
away from those projects.
IF there is compatibility, that is reasonable, but you cannot break
compatibility within AV 4, right? I'm becoming concerned that things are
being moved before the compatibility is in place. Admittedly, this concern
comes in part because James HEAD no longer builds against Avalon HEAD
because of changes to Excalibur packaging.
What do you mean before compatibility is in place? Are you saying we
cannot move anything until all our dependent projects notify us and
tell us that they are ready?
Can we handle a temporary incompatibility that lasts for a day--or at
the most two?
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
