You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

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 
  • [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
  • 24h later: Update download page
  • Remove old versions
  • [ANNOUNCE] email

 

Notes per module:

taverna-engine

 

taverna-common-activities

taverna-commandline

 

 

Draft vote email

 

  • No labels