A crash reporting tool
It enables users to upload their game log and redirects them to different support sites.
Publishing a new release requires to merge all changes from develop
into master
,
bump the version number and add a Git tag. The following steps describe how this
is done.
Be sure that your local workspace is up to date by fetching and merging from upstream
before starting the process.
This guide assumes that you've added movingblocks
as remote for the upstream
repository, e.g., by executing
git remote add movingblocks https://github.com/MovingBlocks/CrashReporter
develop
, local workspace)Update version in gradle.properties
, remove the SNAPSHOT suffix
e.g. version=4.1.0
Update CHANGELOG/README (if necessary)
Commit the changes
e.g. git commit -m "Release 4.2.0"
Create a tag for the release
e.g. git tag -a 'v3.1.0' -m "Version 3.1.0"
Merge develop
into master
(local workspace)
git checkout master
git merge --ff-only develop
master
)Push local master
branch to upstream
git push --tags movingblocks master
Verify that the Jenkins job build succeeded and the new release is working
Close GitHub milestones or issues, if applicable
develop
)gradle.properties
to prepare for next release version=4.1.1-SNAPSHOT
git commit -m "Version 4.1.1-SNAPSHOT"
develop
branch to upstream git push --tags movingblocks develop
This software is licensed under the Apache 2.0 License.