This is a vote to clarify whether we want to focus all our discussions of the new unified container to Avalon 5 (next generation) or Avalon 4.1 (current generation). Here are the implications:
Avalon 4.1 ---------- Current development. We refine current interfaces so that the contracts are more universal and testable. This includes the semantics we have surrounding Context and Serviceable. It also means that we can't clean up the cruft. (deprecated stuff remains deprecated). Avalon 5 -------- New development/clean slate. We leverage our experience with lifecycle interfaces to provide a starting point, but we do not limit ourselves to that alone. We can clean up the cruft, but we must supply a "Compatibility JAR" to allow easy migration from Avalon 4.1 to Avalon 5. We can also shorten the package names (minor, but sometimes helpful). It also helps us unify on a new product. If we continue version 4.1 development we don't have the luxury of challenging any of the current lifecycle interfaces or making things just simply easier to use. Implied in either action is that the existing containers continue to live their lives until the new container is complete. Which is it? Unified Container == Avalon 4.1 or Avalon 5? (Voting to remain open as long as necessary [not less than a week]). Please provide a quick comment why you made your choice (either way). -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
