Skip to content

Git Making a Release

Jump to bottom Edit New page
Paulo Dias edited this page Feb 18, 2014 · 11 revisions

As already known, there are two main branches in Neptus. The master the is the stable branch and is where the official releases are borne. The other branch is the develop. This one is used to integrate the changes and bring Neptus forward.

The version in Neptus is structured as follows: version.MAJOR, version.MINOR, version.PATCH.

Major/Minor Releases

This happens when the develop branch reach a stable or releasable stage. At this stage we should proceed as follows.

Edit the build.xml file and find the following properties:

<property name="version.MAJOR" value="3" />
<property name="version.MINOR" value="0" />
<property name="version.PATCH" value="0" />
<property name="version.DEVELOPER" value="" />
<property name="release.NAME" value="R14.01" />

Examples:

  • For version 3.0.0, set version.MAJOR to 3, version.MINOR to 0, and version.PATCH to 0.

  • For version 3.0.0rc1 (release candidate 1), set version.MAJOR to 3, version.MINOR to 0, and version.PATCH to 0. Additionally set the
    version.DEVELOPER to rc1.

  • Usually we name a release by the year is made. That is the release.NAME. In this case is the 14.01 because is the first of the year 2014. Every minor release increases the value, that is for version 3.1.0 the name will be 14.02. If a patch release is done we add a letter. That is for v3.0.1 will be named 14.01a, and so on.

Add a custom footer
Add a custom sidebar
Clone this wiki locally