So there's 2 issues we're discussing: 1) How to model releases in JIRA 2) Are GA dependencies a prereq for a GA release? Regarding JIRA, we've discussed the following: * Rename ejb3-as-int to ejb3-project. This defines the components used in a release, and its version becomes the "Release Version". * Create ejb3-as5-int, ejb3-as6-int outside the scope of projects/ejb3 and under something like projects/ejb3-as-int. These bring in ejb3-project and also add target-specific configs. They are what's brought into AS. * Add a field for "Fix Component Version" to denote what version of a component has the fix (ie, ejb3-proxy:1.0.0-GA would be a valid value) I think we're still debating the qualifier issue. Since this morning I hold firm in my previous arguments. Carlo has brought up that "GA" means "supported". We don't support any community releases (this is for EAP). And we also don't dictate when EAP is released, so there's nothing blocking someone wanting to adopt a Beta-level component into the platform. Once its there, we have to support it. So I use "GA" to mean "mature" (==stable, feature-complete, tested). And I'm happier applying that label to the whole of EJB3, not to the individual components which comprise it. S, ALR View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4203344#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...