JBoss.orgCommunity Documentation
The chapter describes the various releases and their exit criteria.
Each release is labelled with a version number and an identifier.
ironjacamar-<major>.<minor>.<patch>[.<identifier>]
where
Each release will contain a version number which relates to the feature branch where it was created.
A Major version identifier signifies major changes in the implementation such as a change in the architecture.
The features between major versions can be a lot different, and therefore feature regressions may appear.
A Major version will most likely also mean updates to the configuration and required metadata files for deployments.
A Minor version identifier signifies functional changes to a Major release.
This means that new features have been added to the Major release, and hence may have new configuration options and integration points.
The release is binary compatible to the previous releases -
for example 1.0 vs. 1.1.
A Patch version identifier signifies a binary compatible update to one or more components in a Minor release.
This means that one or more bug fixes to existing components have been integrated in the branch in question.
The release is binary compatible to the previous releases -
for example 1.0.0 vs. 1.0.1.
Each release will contain an identifier which relates to the release quality.
An Alpha release is a snapshot of the main development branch which likely will contain new features.
An Alpha release are made each month (time-boxed) unless the branch is using an identifier as Beta or higher.
The exit criteria for an Alpha release is that the main test suite is passing.
A Beta release contains major features that are considered almost functional complete. This doesn't mean however that all aspects of each feature is complete and therefore not all options will be active.
A Beta release will be made once one or more features are almost functional complete and therefore Beta releases aren't time-boxed, but feature-boxed instead.
The exit criteria for a Beta release is that all test suites are passing.
A Candidate for Release is considered functional complete and candidate for being promoted to a Final release.
A Candidate for Release focuses on functionality, but they are time-boxed to a maximum of two weeks between each release.
The exit criteria for a Candidate for Release release is that all test suites are passing.
A Final release is considered feature complete and stable.
Typically only one Final release will be released from each branch, unless critical or blocker issues are found in the release. Patch releases will be available from our source control system as tags.
The exit criteria for a Final release is that all test suites are passing.
The IronJacamar artifacts are uploaded to the JBoss.org Nexus repository located at:
https://repository.jboss.org/nexus/content/groups/public/
The IronJacamar artifacts are deployed under the groupId of:
org.jboss.ironjacamar
See the User Guide for a complete list of artifacts.
A release of IronJacamar is deployed using:
ant nexus
cd target
./deploy.sh
After the artifacts have been uploaded the release must be promoted in Nexus by logging in and choosing "Promote" and "Close". The path for the staging repository can be used for testing the release.
Note, that this requires Ivy 2.2.0+ and Maven 2.2.1+.
A snapshot of IronJacamar is deployed using:
ant -Dsnapshot=true nexus
cd target
./deploy.sh
Note, that this requires Ivy 2.2.0+ and Maven 2.2.1+.