-
Notifications
You must be signed in to change notification settings - Fork 302
Release Process
Richard Waltman edited this page Jul 11, 2019
·
22 revisions
- Python 3
- On Mac
pip3 install dmgbuildorpip install dmgbuild
The release process is simple. Just run the script "make-release.py" found in the root of the repository.
> python release-script/make-release.py
When prompted, drag and drop the OpenBCIHub folder (or .app file on mac). The script will copy the Hub to the right location. As an option, you can skip this step if you have the latest OpenBCIHub installed in the GUI data directory.
When finished, the script will print the location of the .zip file for upload.
- Create a release in the releases tab in Github
- Paste the verison number in the Tag and the Title fields
- Paste the Change log contents (for this version) in the description
- Check "This is a pre-release" if it's a beta release
- Go to vscode (or whatever)
git fetch --all-
git checkout <tag name>ex:git checkout v4.1.3-beta.2 - Run the release script as described above. Follow the steps.
- On Mac:
- Look for "successfully signed app" if you expect to sign the app.
- A .dmg file will be created.
- On Linux:
- App does not need to be signed
- A .zip file will be made for the 64bit distribution ex.
openbcigui_v4.1.3-beta.2_linux64.zip
- Upload the .dmg/.zip files to the release page
Please feel free to contribute tips, tricks and best practices.