Testing Development Releases

Open source relies on a release early, release often approach to software development. This means that multiple development releases are made before a final release, to allow time for the community to perform tests and report/fix bugs.

JBoss projects are no exception and in general one or more of the following development releases always take place:

  • Alpha
  • Beta
  • Candidate Release 1
  • Candidate Release 2
  • Candidate Release 3
  • Candidate Release <n>

When the code is finally considered stable then a General Availability release is made, ready for use in production.

If you want to make a valuable contribution to the success of a JBoss project then please download and test the development releases as and when they become available. This not only improves the overall quality of the JBoss products but also ensures that you can upgrade to the latest versions without any unexpected side-effects.

Latest Blogs

JBoss Virtual Experience: Presentation Slides
Posted on Jan 5, 2009 10:42:45 PM by Bob McWhirter.

File download support
Posted on Jan 5, 2009 3:42:18 PM by Daniel Roth.

JBoss Virtual Experience
Posted on Jan 5, 2009 3:38:27 PM by Bob McWhirter.

Latest Podcast

RichFaces/Ajax4jsf project discussion with Alexander Smirnov, JBoss Booth, JavaOne 2008 (ogg format)

Ajax4jsf project lead Alexander Smirnov spends a few minutes with JBoss.org/Dev Fu to discuss the history and future of Ajax4jsf. MP3 format is also available.


All Podcasts   ATOM

Developer Spotlight

Scott Marlow

Country:
Title:
Status:

Bio: Scott is a member of the Novell Identity Products development team and contributes to JBoss Clustering, JBoss Cache and JGroups. Scott has also developed distributed application technology, 4GL deve ... More Information