README-releasing-tagging.txt

To generate a new github release

See which is the latest release on https://github.com/SensorsINI/jaer/releases .
Decide the next release version number, e.g. 1.8.1.

You can also see the tags at https://github.com/SensorsINI/jaer/tags. Releases are made from a particular tag.

## Tagging for release
In git terminal, from root of jaer

$ git tag <tag, e.g. 1.8.1>
$ git push origin <tag>

Output will be
Total 0 (delta 0), reused 0 (delta 0)
To https://github.com/SensorsINI/jaer.git
 * [new tag]             1.8.1 -> 1.8.1

After some minutes, the new release will appear on https://github.com/SensorsINI/jaer/releases 
The release notes can then be edited on github web page, if you are logged in and have commit rights.

The release name should then be jaer-1.8.1, for example.

### Deleting tag

If tag is already pushed to origin:

`git push --delete origin 2.1.0`  

View the build results at https://travis-ci.com/github/SensorsINI/jaer .
To add the OAuth secret github token for building, go to https://travis-ci.com/github/SensorsINI/jaer/settings. You need to login with github OAuth.
To make a new token, if needed, login to https://github.com/settings/tokens ,

## Install4j release

1. Install install4j
2. Install your license (tobi has his own by donation to jaer project)
3. Open install4j project (jaer.install4j)
4. Update version number there and save install4j project
5. Do a complete clean and build to make sure classes are clean and all in jaer.jar
6. Generate the installers
7. Put the installers and checksums in new dropbox installers folder
8. Put updates.xml to root folder and push it so install4j can check if there is an update available
9. Maybe update splash screen image and push new png from photoshop
10. Push a tag and generate the github release on github release