> > A long time ago we decided (and voted) to move the excalibur components
> > to avalon-components as soon as they have been officially released.
> > So perhaps it's time now to remember this and move the components?
> I remember this as well. And I think moving excalibur into
> avalon-components is the right thing to do. Though some parts might
> better belong closer to the framework like configuration, logger, and
> lifecycle.
> I just want to make sure we're careful when we do so. The email threads
on
> "excalibur thread update" and "excalibur pool update" seem to point out
the
> importance of this.
I believe that due to the way in which Avalon wants to re-organize and
re-factor the code, it is absolutely imperative that we switch to Subversion
promptly. Otherwise we will shortly have a code base where the active code
has been completely disassociated from its development history.
I don't believe that I can possibly get across how totally unacceptable I
find the current situation.
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
