Win a copy of Event Streams in Action this week in the Java in General forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
  • Campbell Ritchie
  • Devaka Cooray
  • Liutauras Vilda
  • Jeanne Boyarsky
  • Bear Bibeault
  • Paul Clapham
  • Knute Snortum
  • Rob Spoor
Saloon Keepers:
  • Tim Moores
  • Ron McLeod
  • Piet Souris
  • Stephan van Hulst
  • Carey Brown
  • Tim Holloway
  • Frits Walraven
  • Ganesh Patekar

JBoss and WildFly Version Suffix Meanings

Posts: 15
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I am looking to upgrade JBoss 5.1.0 GA to WildFly, sometime early next year. I've been trying to find a good source to explain what all of the suffixes mean. Most of the explanations that I have seen point to the "Software release life cycle" article on Wikipedia. I found that GA is general availability, where I understand that it is supposed to be a polished version that is supposedly free of bugs. What is the real difference between that and the Final version? Is there a standard terminology for these definitions, or are these terms that are being used exclusively by the redhat download page.
Posts: 10445
IntelliJ IDE Ubuntu
  • Likes 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
The stable releases used to be named GA earlier for the JBoss AS community edition. But later it was decided that the GA version suffix should be used for the enterprise edition of the software. So the version suffix for the stable releases of the community edition was switched to "Final". Each version of the community edition, goes through a release cycle of Alpha, Beta, CR and Final (in that order). Each of those can have multiple releases. For example 7.0.0.Alpha1 7.0.0.Alpha2 etc... Alpha and Beta are mainly used by developers who are willing to try out new features and report bugs and also expect that the release might not be stable. CR is the candidate release which a larger set of developers try out since that version gets pushed to Final after limited bug fixes for issues that have been reported.
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!