Community
|
|
||||
|
|
||||
- Community
- JBoss.org Community
- JBoss.org Resources
- Join the Community
- Sign a Contributor Agreement
- Submitting bug reports and submitting feature requests
- Submitting patches
- Testing development releases
- Using the Forums
- Subscribing to Mailing Lists
- Writing or Editing Wiki Articles
- Contribute Code
- Documentation: Contribute New Material
- Join a project team
- The Governance Model
- About JBoss.org
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.