It's better when it's simple

User Tools

Site Tools


Automated Release Builder

Our current process takes lot's of manual steps: Release process

Ideally we'd have a access protected script that does a release based on the current master branch:

  • Ask for
    • RC/Non-RC
    • Release Name
  • do a clean checkout of the master branch
  • run unit tests
  • update message ID and deleted files list and commit/push that1)
  • merge stable into old-stable2), use strategy -Xtheirs
  • merge master into stable, use strategy -Xtheirs
  • update version file, commit & push
  • build tgz
  • move .tgz to
    • update symlink setup there!?
  • update infos
  • Use APIs to announce release?
    • freshmeat?
    • IRC channel?
Alternatively check that this has been done before
FIXME how to check if this has been done already for a previous release candidate
devel/ideas/release_builder.txt · Last modified: 2013-10-28 20:04 by andi

Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
CC Attribution-Share Alike 4.0 International Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki