-
Notifications
You must be signed in to change notification settings - Fork 31
How to create a new release version
Bernhard Thiele edited this page Mar 19, 2016
·
13 revisions
Using the Github release workflow. Todo document it.
cd Modelica_DeviceDrivers
rm -r Incubate/
# Generate help html documentation (in Dymola)
# Remove Incubate entry from package.order file
# Check whether to adapt README.md, UsersGuide.mo (ReleaseNotes) and librarinfo.mos
# ...
- Remind https://github.com/xogeny/impact/blob/master/resources/docs/modelica2015/paper/impact.md#impact-on-library-developers for future releases.
- Write release script using https://github.com/aktau/github-release?
The old way of releasing. It is outdated now.
This is just a little memo how to create a release version from the master branch. The following shell commands were used to create the v1.1 release:
cd Modelica_DeviceDrivers
mkdir /tmp/MDD; cp -r * /tmp/MDD
git checkout -b tmp
# in case status for cut of release is at an point different from HEAD:
# git reset --hard <hash of where the release should be cut from>
git checkout release
git merge -s ours tmp
rm -r *
mkdir "Modelica_DeviceDrivers 1.1"
cd Modelica_DeviceDrivers\ 1.1/
cp -r /tmp/MDD/* .
rm -r Incubate/
mv README.md screenshot.png ..
# Generate help html documentation (in Dymola)
# Remove Incubate entry from package.order file
# might want to adapt README.md, UsersGuide.mo (ReleaseNotes) and librarinfo.mos
cd ..
git add -A .
git commit --amend -m"Created v1.1 release"
git tag v1.1
git push origin release
git push --tags origin v1.1
git branch -D tmp