THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
Release manager: Stian Soiland-Reyes
Adapted from Taverna's release procedure.
- Email dev@taverna to say a release is imminent
https://lists.apache.org/thread.html/Zftr9wrc9obun4b - Check Jira for issues on the corresponding components
- Create and maintain a Jira task to keep track of the subtasks (this page)
- Update JIRA Fix For versions
- Prepare build machine
- GPG keys
- Fresh checkouts
- Git config
- Check Maven repository write access
- Close old staging repos
- Figure out release order
taverna-engine
taverna-common-activities
taverna-commandline
- Verify build
- Fix versions in pom.xml
- Prepare release candidate
- Deploy release candidate
- Locate staging repository
- Upload to dist.apache.org
- Prepare vote email
- Announce Vote on dev@taverna
- Discuss email
- Tallying the vote
- Vote on general@incubator
- Tallying the incubator vote
- Moving dist
- Releasing Maven repo
- Update download page
- Remove old versions
Notes per module:
taverna-engine
taverna-common-activities
taverna-commandline
Draft vote email