> I'm not trying to have an argument dude....
Neither am I, Paul. :-) You indicated that "some time ago the JAMES
community got a bit pissed off with 'Avalon' and wanted rid of it", and that
this was one reason why you felt it important to distinguish between the
different aspects of the Avalon technologies. I am trying to get your take
on what you thought that the real issues were.
> There was an element of confusion concerning the differerence between
> our deliverables.
I can appreciate that. Especially since there was a transition to a new
(and different) version of the parts in that time frame. As you note, one
of the really helpful things that you did was to migrate the existing code
to the modified interfaces and help maintain the correct levels of Avalon
code (not just Phoenix, but also Excalibur, Cornerstone and other
dependents). That smoothed over quite a few feathers.
Right now we run something of a hybrid version, where we are current on some
areas, and backlevel on others. We expect to move forward after our next
release, when we'll make necessary changes.
--- Noel
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
