Difference between revisions of "Release Checklist"

From Liberty Eiffel Wiki
Jump to navigation Jump to search
Line 5: Line 5:
 
* create new bootstrap germ code
 
* create new bootstrap germ code
 
resources/smarteiffel-germ/make_germ.sh
 
resources/smarteiffel-germ/make_germ.sh
* create a branch for the next release
+
* create a local branch for the next release
 
git branch bell
 
git branch bell
  +
* create a bell branch in the github repo (via web interface?)
 
* push it to savannah
 
* push it to savannah
 
git checkout bell
 
git checkout bell

Revision as of 21:19, 28 April 2016

This is WIP. Please update if you think of any missing detail. The target is to include all necessary command line commands (where applicable)

  • cleanup Testsuite
  • update LIBERTY_VERSION
  • create new bootstrap germ code
resources/smarteiffel-germ/make_germ.sh
  • create a local branch for the next release
git branch bell
  • create a bell branch in the github repo (via web interface?)
  • push it to savannah
git checkout bell
git push upstream bell
  • remove all tools and libraries which are not sufficiently mature to be included in the release
    • for Bell these are:
cluster smarteiffel/generation/run
smarteiffel/commands/run.e
edc-new, edc
lib/mmi?
mock, effect tool? (at least we have no documentation about them, have they been in adler?)
src/staging
src/lib/net/ezmq
wrappers: cairo, database/postgresql, ewlc, llvm, zmq, xml
  • switch ET to use the new branch
  • create release candidate
git tag <release_name>-rc1
  • collect RC feedback on our mailing list
  • create the final release tag
git tag <release_name>
  • create release debian packages
HOW?
  • create tarball and put on FTP server
  • write announce email to our mailing list and as news on savannah
  • switch ET back to use the master branch
  • plan the next release (tickets on savannah)