Skip to content

Latest commit

 

History

History
71 lines (43 loc) · 2.01 KB

RELEASING.md

File metadata and controls

71 lines (43 loc) · 2.01 KB
Raw

To prepare the release:

Add release notes to

  • website/history.html

Update the version number in

  • RELEASING.md (this file)
  • README.md
  • README.txt
  • build.xml
  • website/index.html
  • website/history.html

To push a new release to Maven Central:

Generic instructions

  1. git checkout master
  2. git pull
  3. ant clean
  4. ant maven2
  5. cd dist/maven2
  6. Sign the files:
$ gpg -ab xom-1.3.9.pom
$ gpg -ab xom-1.3.9.jar
$ gpg -ab xom-1.3.9-javadoc.jar
$ gpg -ab xom-1.3.9-sources.jar

  1. $ jar -cvf bundle.jar xom-1.3.9.pom xom-1.3.9.pom.asc xom-1.3.9.jar xom-1.3.9.jar.asc xom-1.3.9-javadoc.jar xom-1.3.9-javadoc.jar.asc xom-1.3.9-sources.jar xom-1.3.9-sources.jar.asc

  2. Login to oss.sonatype.org.

  3. Select staging upload in the left hand column.

  4. Upload Mode: Artifact Bundle

  5. Select xom/dist/maven2/bundle.jar and press Upload Bundle. If bundle.jar doesn't work, try individual artifacts instead.

  6. Select staging repositories in the left hand side.

  7. Scroll to the bottom and find the bundle you just uploaded. Select it.

  8. Close the repository. Wait.

  9. Release the repository.

  10. Tag the release on github.

  11. Update README.md with the new version number.

To update the website:

  1. sftp the files to IBiblio including the assorted jar and zip files

  2. Upload the various binary archives to Github as release assets by editing the latest release on https://github.com/elharo/xom/releases/

  3. ant website

  4. cd dist/website

  5. Use gcloud to push to xom.nu with the elharodotcom credentials:

    ~/xom/dist/website$ gcloud app deploy --no-promote --project=xom-website

  6. Check that the staging site—URL found in the output of gcloud app deploy—looks OK. If it is, promote it from the cloud console using Versions > Migrate Traffic.