steps to create a new release

  • check out project into a new branch, say release-x.y.z

  • update the WEINRE_VERSION variable in as appropriate

  • add changelog to weinre.doc/ChangeLog.body.html

  • fix other doc as necessary

  • perform full build with:

    • cd into and run ant build-archives
  • run the smoke test (see below) to ensure delicious smoky flavor

  • upload the archives wherever

  • make sure you can download those archives!

  • commit release changes:

    • git add .
    • git commit -m "update for release x.y.z"
  • merge branch onto master:

    • git checkout master
    • git merge --squash release-x.y.z
    • git commit -m "update for release x.y.z"
    • git push
    • git tag -a x.y.z
    • git push --tags
  • copy archives into temporary download location

  • update npm

    • run cd
    • run npm publish
  • update apache cms pages:

    • not ready for prime time
  • prepare for blessed Apache version

    • not sure how to do this yet

smoke test

The smoke test involves testing the archives:

  • apache-cordova-weinre-{VERSION}-bin.{ARCHIVE}
  • apache-cordova-weinre-{VERSION}-doc.{ARCHIVE}
  • apache-cordova-weinre-{VERSION}-src.{ARCHIVE}

The archives are built via ant build-archives and are available in

smoke test - bin

  • unzip the -bin archive and cd into it
  • run ./weinre --help make sure help works
  • run weinre
  • in your browser open the main page, eg http://localhost:8080
  • poke around the demo, make sure it works
  • should add some variations on starting with used port, etc

smoke test - doc

  • unzip the -doc archive
  • browse all pages

smoke test - src

  • unzip the -src archive and cd into it
  • run cd
  • run cp
  • run ant build-archives
  • run the smoke test on the built archives, recursively