The more I think about it, the less I like Stage and Extension being in the Avalon namespace. I just have this nagging feeling that these tags will be superceded in the future by something else.
quoting Paul from a few weeks ago: "you worry too much". As long as it is documented (rather than just code) and unit tested it is also possible to have stuff be superceded by other stuff. My guess is that there's now a handful of people up to speed on all the meta stuff and that several minds are converging on how to do it; you even have a sort-of roadmap for getting it set up. Implement one way, release a milestone, validate in real life.
A phrase often heard among XPers: "we can always change it later".
I propose that the tags currently named @avalon.stage and @avalon.extention
be placed in the "lifecycle" namespace making their names be @lifecycle.stage
and @lifecycle.extention.
+1. I disagree with the notion that all avalon containers must know what a lifecycle extension is (though I agree all containers developed at avalon.apache.org should), and this would make clear that some container developers can / should / are likely to ignore the lifecycle stuff.
cheers,
- Leo
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
