Page History

...

Email dev@taverna to say a release is imminent
https://lists.apache.org/thread.html/Zftr9wrc9obun4b
Check Jira for issues on the corresponding components
Taverna Engine -
deferred:
Jira
server ASF JIRA
serverId 5aa69414-a9e9-3523-82ec-879b028fb15b
key TAVERNA-871

Blocking:
Jira
server ASF JIRA
serverId 5aa69414-a9e9-3523-82ec-879b028fb15b
key TAVERNA-94
(should be mentioned in release notes)
Taverna Common Activities
Taverna Command-line Tool
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
Close and locate staging repository
Upload to dist.apache.org
Prepare vote email
Test the release candidates on alternate machine
[VOTE] email on dev@taverna
[DISCUSS] email on dev@taverna
[RESULT][VOTE] email to dev@taverna (tallying the vote)
[VOTE] email on general@incubator
[RESULT][VOTE] email to general@incubator
Publishing on dist (svn mv)
Releasing Maven repo
Update git tags (e.g. 3.1.0-incubating-RC3 -> 3.1.0-incubating)
Update SNAPSHOT versions (e.g. 3.1.0-incubating-SNAPSHOT -> 3.1.1-incubating-SNAPSHOT
Depend on new stable versions from other repositories' <properties> section
Publish updated javadocs
Draft [ANNOUNCE] email
24h later: Update (and add links to) download pages
24h later: Remove old versions from dist
24h later: Send [ANNOUNCE] email
Update release procedure with any new/changed routines & tips