-
Notifications
You must be signed in to change notification settings - Fork 0
Groovy :: Dry Release
I've put the required sources into a rosinstaller in yujin_release for each ros version (following instructions here). To download the release tools and our stacks to be released:
> sudo apt-get install python-rosdep python-rospkg python-rosinstall python-rosrelease
> rosinstall /opt/release https://raw.github.com/yujinrobot-release/yujin_release/master/release-groovy.rosinstall
You have to put rules for each repo type in the releases stack as described here. Should only need to do this for any new git account or svn repo. Typically don't worry about it - already done.
Similarly you also have to write a rule for the stack that you want to release. If upgrading don't worry about it - already done. If adding a new stack, then simply copy one of the yujin/stonier stacks to suit. Remember to make version: null
- Prerelease : really important, you'll lose days of work if you don't do this (and piss Tully off).
-
Version bump : update the version number in the stack
CMakeLists.txt. Commit with the version number as the message, e.g.git commit -a -m "0.1.9". This makes it easy to track. - Release : create new versioned release (use the same version number as above).
rosrelease-legacy zeroconf_avahi_suite 0.1.6 groovy
This will create a version tag, distro named branch on your repo.
- ChangeLists : check the project commits between the last update and this one and finally update the changelist on ros wiki (e.g. http://ros.org/wiki/kobuki/ChangeList)
- Wiki - dry instructions
- Bloom - wet instructions
- Jenkins - wet builds
- DebBuild List - list of current build status'.
- Build System SIG
- Source Tarballs
major.minor.patch
- If it's a minor in-release change, bump the patch number.
- If it's a big change, bump the minor number.
- If releases are no longer compatible going from one ros to the next, bump the minor number.
- If it becomes stable/mature, bump straight to 1.0.
- If it's a radical extremist terrorist style change, bump major.
Haven't tried these yet, but it should be possible to do local prerelease tests in a chroot.