I am not sure whether you are for or against the binding of a certain release of ContainerKit and Info into Phoenix.
Please clarify...
- Paul
Stephen McConnell wrote:
Paul Hammant wrote:I'm still not happy with the demotion of phoenix compoents to alpha/sandbox.As one of the Avalon comitters active in the process of the info and containerkit package development - I can absolutely assure you that neither package were based on existing code imports fro Phoenix - concept yes - code no. They both represented new content - some of which I contributed to. They both represent alpha status. Both represent unqualified and unvalidated content. They both represent subjects for review and consideration. Thaey both hold room for improvement.
Within this context, what are you unhappy about ?
Steve.
Stephen McConnell wrote:
Paul Hammant wrote:Discussed at length.....................+1
Proposal -> Container kit removed from avalon-sandbox, place back in Phoenix CVS under Phoenix
packages. ContainerKit jar still produced, containing new classes. That jar only available as
part of the Phoenix binary distros. It is not listed as product or separately available as a
component, it is merely part of the internals of Phoenix. One jar of many. Teams making uber
designs may still be inspired by CK, or not.
Real companies are using Phoenix in live scenarios. It does not help when components look like
they are alpha, when they are not. It may be that there is not long life to that comp (given
uber) but that does not mean that it should be downgraded to ALPHA or placed in a sandbox.
My vote = +1
You may want to consider doing the same thing for the loader and info packages.
Steve.
-- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
