Google Git
Sign in
apache / fineract-cn-stellar-bridge / refs/heads/master
commitc1ead7b8e1dceae64e611724f34958d1610678a1[log] [tgz]
authorMyrle Krantz <myrle@apache.org>Wed Jul 18 15:13:59 2018 +0200
committerMyrle Krantz <myrle@apache.org>Wed Jul 18 15:13:59 2018 +0200
treed4cf3942e317ff5ed68c9873e313623b79f35829
parent7b3437577d246d615b8c1398817fe1b5eee39aa4 [diff]
Began work on mapping to Stellar currency issuer, in preparation for
making outbound transactions.  Had first go at inbound transactions.
24 files changed
tree: d4cf3942e317ff5ed68c9873e313623b79f35829
  1. api/
  2. component-test/
  3. gradle/
  4. service/
  5. .gitignore
  6. build.gradle
  7. gradlew
  8. gradlew.bat
  9. HEADER
  10. LICENSE
  11. NOTICE.txt
  12. README.md
  13. settings.gradle
  14. shared.gradle
README.md

Apache Fineract CN / Stellar Bridge

Versioning

The version numbers follow the Semantic Versioning scheme.

In addition to MAJOR.MINOR.PATCH the following postfixes are used to indicate the development state.

  • BUILD-SNAPSHOT - A release currently in development.
  • M - A milestone release include specific sets of functions and are released as soon as the functionality is complete.
  • RC - A release candidate is a version with potential to be a final product, considered code complete.
  • RELEASE - General availability indicates that this release is the best available version and is recommended for all usage.

The versioning layout is {MAJOR}.{MINOR}.{PATCH}-{INDICATOR}[.{PATCH}]. Only milestones and release candidates can have patch versions. Some examples:

1.2.3.BUILD-SNAPSHOT
1.3.5.M.1
1.5.7.RC.2
2.0.0.RELEASE

License

See LICENSE file.