Quick question to everyone, since it has been brought up:
Is Avalon Meta officially endorsed as the Avalon-Wide meta spec?
If so, when did we vote for it to become that, or as part of what
discussion did we reach that consensus?
It is currently my understanding that (which is similar to Berin's):
1. Meta is released - but then again, so is Fortress Meta, ECM and
lots of other stuff. It means we have to look after backwards
compatibility, but not any special acceptance of the whole
package at framework level.
2. The last attempt to get a framework-wide metainfo resulted in this:
http://marc.theaimsgroup.com/?l=avalon-dev&w=2&r=3&s=vote+avalon+meta&q=
b
See the [VOTE] Lifecycle Extensions, [ANTI-VOTE] and [ReVote]
messages.
3. Avalon Meta has been Merlin-specific so far, and released as part of
Merlin.
OK, so what did I miss / forget?
Let's just get this thing out of the way...
/LS
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
