-
Notifications
You must be signed in to change notification settings - Fork 0
Release procedures
Andre Merzky edited this page Dec 12, 2013
·
2 revisions
The RADICAL group has too coordinate the release of several software packages. The release manager / development leads are:
- radical.utils: Andre Merzky
- synapse: Andre Merzky (depends on radical.utils)
- saga-python: Ole Weidner (depends on radical.utils)
- saga-pilot: Ole Weidner (depends on saga-python, radical.utils)
- bigjob: Melissa Romanus / Andre Luckow (depends on saga-python)
- troy: Andre Merzky (depends on saga, utils, bigjob, saga-pilot)
- On a planned release, the respective repository's master branch is prepared and tagged as release candidate.
- downstream package managers are informed by mail to the radical-cybertools mailing list, and asked for testing against the RC
- only when all downstream packages are tested ok (as confirmed on the same mailing list), the RC is promoted to release and pushed to pypi.