Development

Information on development process...

Branches

• [development] - cutting edge development, please branch from here if you wish to submit patches
• [release-x.y] - x.y release path - open until final bugs are completed and x.y is released. it will be merged to master at that point (releases)
• [maint-x.y] - x.y maintenance path
• [master] - latest release branch

Other branches are transient at this time.

Performing releases

Notes on performing release for version x.y

1. create release-x.y branch from development
2. update version numbers
3. build and test release candidate version
4. merge to master
5. tag release vx.y
6. build from master and release x.y
7. copy generated docs to docs/x.y on rundeck.org site
8. copy distribution files to github downloads

Maintenance

Notes on maintenance branches for version x.y(.z)

1. create maint-x.y branch from release tag branch (e.g. tag "v1.2")
2. create maint-x.y.z branch from maint-x.y
3. update version numbers
4. dev, build, test
5. perform bugfix merges separately to downstream development/release branches as appropriate (not to master)
6. merge maint-x.y.z into maint-x.y
7. tag release vx.y.z: git tag -a vx.y.z
8. build from tag vx.y.z and release x.y.z
9. as above
10. as above