DUE TO SPAM, SIGN-UP IS DISABLED. Goto Selfserve wiki signup and request an account.
...
| Pre-Release Qualifier | Meaning | Example |
|---|---|---|
| snapshot+<x> | A release currently in development. The contents of x are optional, freely defineable, and mean something only to the person creating the snapshot. | 1.1.0-snapshot+myrlesbuild23 |
| alpha.<whole number> | We know or expect there to be problems, but solicit testing from interested individuals. In case there are multiple alphas, they are numbered. The larger the number, the more advanced and (theoretically) more stable the release. | 1.1.0-alpha.0 |
| rc.<whole number> | Release Candidate. This release is a candidate to become the final proposed version. If no serious bugs are found, the -rc tag will be dropped, and the contents of this release will be declared stable. | 1.1.0-rc.0 |
| <none> | If there's no pre-release qualifier, it's a release, not a pre-release. | 1.1.0 |
First release
Our first release of Apache Fineract will have a major version of 0. It is not yet determined when we will iterate that release version to 1.
Alpha releases
When we want new features to get wide testing before we enter the formal stabilization period, we will sometimes release alpha versions. There is no requirement to do multiple alpha releases. We could just jump straight to "rc.0". However, there are circumstances where a beta can be useful: for example, if we are unsure of a decision and want to get wider user feedback before solidifying it into a formal release candidate.
...