Release Instructions
Encore does not currently have an automated release system. These release instructions have been created in order to avoid mistakes while making a release.
Instructions
Build the UI app package
- Pull the latest encore-matlab-ui repository changes and ensure everything is up-to-date by running:
git pull; git submodule foreach --recursive "(git checkout master; git pull)"; git status
- Open MATLAB
- Change directory to the root encore-matlab-ui submodule directory within the encore-matlab repository
- Add the lib and src directory and their child directories to the MATLAB path
- Open Encore UI.prj
- Click "Refresh dependencies"
- Close the project
- Edit
encoreui.app.App
and make sure the version matches the next release version number - Package the app by running:
package
Build the toolbox package
- Pull the latest encore-matlab repository changes and ensure everything is up-to-date by running:
git pull; git submodule foreach --recursive "(git checkout master; git pull)"; git status
- Open MATLAB
- Change directory to the root encore-matlab directory
- Generate the documentation from the wiki by running:
site
- Replace src/main/resources/docs with target/site
- Add the lib and src directory and their child directories to the MATLAB path
- Edit
encore.app.App
and make sure the version matches the next release version number (this should generally be the same number used while building the UI app) - Package the toolbox by running:
package
The releasable toolbox (Encore.mltbx) is now under the target directory.
Create a new release on GitHub
- Go to https://github.com/Encore-DMS/encore-matlab/releases
- Click "Draft a new release"
- Enter the tag version as the Encore version number being release (e.g. 2.0.2.1)
- Enter the release title in the format "ENCORE_VERSION (MAJOR.MINOR-DEV_STAGE.REV) x64" (e.g. 2.0.2.1 (2.0-rc1) x64). The third position of the full ENCORE_VERSION indicates the DEV_STAGE: 0 = alpha, 1 = beta, 2 = release candidate, 3 = release. The forth position indicates the REV.
- Enter the release notes
- Attach the Encore.mltbx file
- Mark the build as pre-release if the dev stage is alpha, beta, or release candidate
Update the Encore-DMS website
- Pull the latest encore-dms.github.io repository changes and ensure everything is up-to-date by running:
git pull; git submodule foreach --recursive "(git checkout master; git pull)"; git status
- Open the _config.yml file
- Replace the "version" property value with the new Encore version number
- Commit and push the change to GitHub