Developerhowtorelease

How to release to a new version

Update documents

• README.html in ontop-protege. This file will be displayed in the Protege Plugin Update window.
• README.md in quest-distribution. This file will be uploaded to SourceForge
• update.properties file in ontop-protege. This is the configuration file for Protege plugin Auto Update

Create a git branch for release

$ git checkout develop
$ git checkout -b release/v-number

Update the version numbers

Update pom.xml files by Maven plugin to a SNAPSHOT version:

$ mvn versions:set -DnewVersion=2.0.0-SNAPSHOT 

Build maven packages

$ mvn release:clean

# Preparing the release will create the new tag in git and automatically push to github
# When 100% sure, you can skip the test by `-Darguments="-DskipTests"`
$ mvn -DperformRelease=true release:prepare

# stage the release
$ mvn release:perform 

# Or stage from a Git tag
# mvn release:perform  -DconnectionUrl=scm:git:git@github.com:ontop/ontop.git -Dtag=ontop-1.17.0

Build Ontop bundles

$ ./build-release.sh 

Test

• Travis-CI
• run ontop-test module
• run protege plugin tests
• test CLI
• test Jetty bundle

Release

• Deploy the packages to SourceForge via sftp.

$ sftp user,ontop4obda@frs.sourceforge.net
$ cd /home/pfs/project/o/on/ontop4obda
# sftp://ghxiao,ontop4obda@frs.sourceforge.net/home/pfs/project/o/on/ontop4obda

• Stage the artifacts in sonatype https://oss.sonatype.org

• Update Home and OntopReleases of this GitHub Wiki

• Send release emails to several mail lists

Prepare for next development iteration

Update branches:

Merge the tag for the release to master and the release branch to develop

$ git checkout master
$ git merge v-number # tag

$ git checkout develop
$ git merge release/v-number #branch 

Time for celebration!