I don't fully understand your question. WildFly is a community project and is free for use and available in openly accessible Maven repos.
JBoss EAP on the other hand is a product, certain versions of which are available under a paid subscription and certain versions of which have been made available under the developer program for free to use outside a production environment.
Yeah jaikiran, sorry my poor english.
Previously there are JBoss AS as community version, with formal binary releases on all three levels of versioning (X.X.X), with last release as 7.1.1.
Now, with WildFly, what types of releases community should expect for? Last say, for each implementation version (8.X) how much minor version (8.0.X) should be expected?
1 of 1 people found this helpful
WildFly is 'only' a renaming of JBossAS to be more clear what is the community and the EAP version.
The current EAP6 is based on JBossAS7.x, the latest version of 7.x is available from github but there are no further releases or binaries for download.
See different EAP/AS7 discussions.
WildFly continue as the community version and the next EAP will be based on that. Here you will have further releases and it depend on several decisions whether the next release is a minor or major version. So there is no fixed schedule like after Y minor versions a new major version will be released.
Does that make sense to you?
Until now I do not have seen WildFly as a simple renaming of JBoss AS, since even web container has changed, but this is not relevant to me.
For the question "as is" JBoss AS have not "fixed schedule" too, but between major or implementation versions always was expected some minor version, this is the path to be followed?
Until now I do not have seen WildFly as a simple renaming of JBoss AS, since even web container has changed
Well it is a rename with it's first release being the next major release, being a major release it can be expected to contain major changes ;-)
OK, thanks, I didn't realize that until now.