Correct.... That is the way releasing releases works. You have a reporting issue where you mention in which release it has to be fixed. If an issue is fixed it is in CVS-Head... so you can checkout that. Besides that, there is a roadmap that shows on all issues that need to be fixed before a release is done. Often it also includes a 'guestimate' for a releasedate. In this case, 3.2.3 is not released yet, so it is not in binary or even tagged in cvs. 3.2.2 SOA1 is for inclusion in the JBoss SOA release and will not be a separate jBPM release. If it is tagged in CVS I do not know. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4112682#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...