Skip to content

Latest commit

 

History

History
16 lines (15 loc) · 1.02 KB

RELEASING.md

File metadata and controls

16 lines (15 loc) · 1.02 KB

Releasing

  1. Ensure you are set up for deploying to Maven Central.
  2. Ensure you're using JDK 8.
  3. Run mvn release:prepare release:perform and follow the instructions.
  4. Enter the release version when prompted or press Enter for default (Please double check the version if you do so).
  5. Enter the next development version when prompted or press Enter for default (Please double check the version if you do so).
  6. Add release notes to the newly created tag on https://github.com/spotify/dataenum/releases.
  7. Once the new release has propagated to Maven Central, update the last.version property in the root pom.xml to indicate the right version. Failing to do so means opening up for this:
    1. last.version points to version 14.
    2. version 15 is released, adding the method foo(Integer i).
    3. version 16 is released, changing signature of foo to foo(Boolean b). This is an API-breaking change that goes undetected, since japicmp is only checking against version 14, where foo didn't exist.