I've created a 9.x branch in the WildFly repo on github.[1] From this point forward, work on the 'master' branch will be targeted toward the WildFly 10 release. If you have a change that needs to go into WildFly 9 (i.e. for 9.0.0.CR2), you will need to submit two pull requests: one against the 9.x branch, and one against master. The latter ensures your fix doesn't get dropped in WildFly 10. If you create a PR against 9.x, be careful in the github UI when you submit it. Even if your local branch was based on 9.x, github doesn't recognize that and by default will create the PR against master. You need to use the pulldown to select 9.x. For WildFly Core I created a 1.x branch last Friday, and master now targets 2.0, which will be the core version using in WildFly 10. Our intent is to produce a WildFly 10.0.0.Alpha1 on or around May 19, with another alpha following every two weeks. These are meant to be time-boxed releases, produced according to schedule with whatever is ready included. Best regards, -- Brian Stansberry Senior Principal Software Engineer JBoss by Red Hat [1] https://github.com/wildfly/wildfly/tree/9.x