Committing Snapshot Versions

When the changes have reached a stage where they are consistent and working they can be published as an interim snapshot. This is not a release but makes the current state available to the rest of the team and developers.

To do this you should first do some 'housekeeping' as folows:

• make sure the feature version in feature.xml correctly reflects the plugin version updates that you have made
• make sure the feature history is up to date in feature.properties
• update the copyright property field in feature.properties
• compute dependencies in the feature.xml.
• update the copyright headers of all changed files (you can use the RelEng 'fix copyrights' tool to do this automatically from the repo)
• Also in pom.xml update the version of the feature to be a SNAPSHOT (not RELEASE), e.g. 3.5.1-SNAPSHOT
• Update pom.xml files in the releng project to reflect the version of Eclipse and Rodin that you are targeting.
  • Version number of tycho: Currently, we use 2.7.5 (not the latest version) (Tycho @ Maven Central Repository)
  • Version number of maven-resource-plugin: Currently, we use 3.3.0 (Maven resource plugin @ Maven Central Repository)
  • Eclipse repository: Currently, we use Eclipse 4.22, i.e., https://download.eclipse.org/eclipse/updates/4.22/.
  • Rodin platform update: Currently, we use Rodin 3.7, i.e., https://rodin-b-sharp.sourceforge.net/core-updates/3.7

Commit and push these changes into your fork

Raise a pull request from your forked development branch to the main eventB-soton git repository, 'latest' branch and select at least one suitable reviewer to approve the changes.