As the PR is frozen the latest master release should be 0.8-SNAPSHOT

This is a placeholder for JIRA tickets:https://java.net/jira/browse/javamoney (as JIRA 4 can't be properly connected from java.net)

Travis-CI has become a liability.

Builds have been temporarily disabled for public repositories due to a negative credit balance. Please go to the [Plan page]
(https://app.travis-ci.com/organizations/JavaMoney/plan) to replenish your credit balance or alter your Consume paid credits for OSS > setting.

Where that "Consume paid credits" just leads to an error, so abandonTravis and kick it off every repository that does not already use GH Actions (like this one)

Using javamoney in different projects raises the question of a BOM similar to JBoss or Spring etc. allowing to apply the right dependencies of API, RI and potential 3rd party libraries in a single place.

JFrog announced it will shut down Bintray and JCenter by the end of April: https://jfrog.com/blog/into-the-sunset-bintray-jcenter-gocenter-and-chartcenter/

This affects multiple aspects of the JavaMoney build process or download content:

• Maven - Fix Permissions for Sonatype Nexus: https://issues.sonatype.org
• Maven - Change additional repositories in every relevant POM. While "Artifactory installations with remote repositories configured against Bintray and Centers will not be affected by this sunset." is worth clarification, it does not sound like this applies to anything other than an Artifactory client but not e.g. a build job on a Circle-CI, the snapshot repositories like https://oss.jfrog.org/artifactory/oss-snapshot-local are most likely going away at least those few weeks after the sundown
• Maven - Deployment to Bintray Snapshot repositories won't work anymore. Trying that after May 1st will certainly break the build, so any use of CI_DEPLOY_USERNAME/PASSWORD or equivalent must point to something else, probably a Sonatype/Nexus user with appropriate permission to perform snapshot deployments