[alesj]

ControllerMode == asynchronous (requested by Bela)

http://jira.jboss.com/jira/browse/JBMICROCONT-265

or the error handling mechanism (requested by Julien)

http://jira.jboss.com/jira/browse/JBMICROCONT-266

[alesj]

Another in/uncallbacks in BeanMetaDataBuilder
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=130106

http://jira.jboss.com/jira/browse/JBMICROCONT-268

Plus this one was missing as well:
- http://jira.jboss.com/jira/browse/JBMICROCONT-269

[adrian.brock]

Don't schedule things for GA.
Everything should be done by CR1 (especially api changes).

In principle GA could/should just be
svn copy micrcontainer/tags/2.0.0.CR1 microcontainer/tags/2.0.0.GA
(it can't actually be that because the poms have to be updated with the version :-)

That doesn't mean we can't do fixes in the GA, it just means we shouldn't be
expecting to do so until after the first CR1 is released.

[kabirkhan]

I am working on the aop-mc-int xml parsing. Am I OK to commit to aop-mc-int?

It will be
-updates to the tests, which are mostly broken anyway due to the xml parsing
-updates to the org.jboss.aop.microcontainer.beans.metadata package, which is unused until the SingletonSchemaResolverFactory is switched over to use org.jboss.aop.microcontainer.beans.metadata.AOPDeployment

[adrian.brock]

I am working on the aop-mc-int xml parsing. Am I OK to commit to aop-mc-int?

Yes. The issue was I didn't people to update the maven snapshots, but it is too
late now, Ales already did it. :-)