-
Notifications
You must be signed in to change notification settings - Fork 827
HowTo Release
Thomas Heigl edited this page Apr 11, 2021
·
4 revisions
A GPG key is required for signing the artifacts. See https://central.sonatype.org/pages/working-with-pgp-signatures.html.
- On latest master perform a mvn release:
mvn clean
mvn release:clean
mvn release:prepare
mvn release:perform
- Publish the release via Sonatype
- Login at https://oss.sonatype.org/ with your sonatype username/password
- Go to "Staging Repositories" and select the appropriate kryo repository
- "Close" the repository, and when it's closed "Release" it
- Document the release
- Create the compatibility report using japi-compliance-checker:
- run
https://github.com/lvc/japi-compliance-checker kryo-$OLDVERSION.jar kryo-$NEWVERSION.jar
- move the created
$OLDVERSION_to_$NEWVERSION
folder tocompat_reports/kryo/
andgit add
it
- run
- Update the README Recent Releases and Installation With Maven sections
- Describe the new release to https://github.com/EsotericSoftware/kryo/releases, and add the
kryo-$NEWVERSION-all.zip
from thetarget/
folder to the release page
- Create the compatibility report using japi-compliance-checker: