THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
- Run
./sbt releaseand answer the version number prompts.- Close the staging release repository afterwards by logging in to https://repository.apache.org/#stagingRepositories and finding the appropriate
orgapachelogging-NNNNrepository.
- Close the staging release repository afterwards by logging in to https://repository.apache.org/#stagingRepositories and finding the appropriate
- Check out the created tag and run
GPG_KEYID=mykeyid ./create-distributions.sh 12.0 <tag-name>- FIXME: binary distributions may not be signed by default; make sure to sign them! As a workaround, use the following bash script:
cd target; for f in *.zip *.gz; do shasum -a 256 $f >$f.sha256; shasum -a 512 $f >$f.sha512; done
- FIXME: binary distributions may not be signed by default; make sure to sign them! As a workaround, use the following bash script:
- Commit those to https://dist.apache.org/repos/dist/dev/logging/log4j/scala for staging (removing previous release candidates as necessary).
- Commit the site to github pages for previewing.
- FIXME: this currently requires manually aggregating the API docs from each
target/scala-2.xx/api/directory intotarget/site/api/2.xx/.
- FIXME: this currently requires manually aggregating the API docs from each
- Perform a release email and follow the usual release process as Log4j Core does.