Difference between revisions of "Release Checklist"

From Liberty Eiffel Wiki
Jump to navigation Jump to search
(debian build)
Line 22: Line 22:
 
wrappers: cairo, database/postgresql, ewlc, llvm, zmq, xml
 
wrappers: cairo, database/postgresql, ewlc, llvm, zmq, xml
 
* switch ET to use the new branch
 
* switch ET to use the new branch
  +
** echo "bell" > ~/branch on ETs account
  +
** change website/et/html_templates/head.html to make ET output tell people which branch is being tested...
 
* create release candidate
 
* create release candidate
 
git tag <release_name>-rc1
 
git tag <release_name>-rc1
Line 33: Line 35:
 
* write announce email to our mailing list and as news on savannah
 
* write announce email to our mailing list and as news on savannah
 
* switch ET back to use the master branch
 
* switch ET back to use the master branch
  +
** echo "master" > ~/branch on ETs account
 
* prepare changelog for the third release
 
* prepare changelog for the third release
 
* plan the next release (tickets on savannah)
 
* plan the next release (tickets on savannah)

Revision as of 21:23, 2 May 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
    • echo "bell" > ~/branch on ETs account
    • change website/et/html_templates/head.html to make ET output tell people which branch is being tested...
  • create release candidate
git tag <release_name>-rc1
work/packaging/build_debian.sh -rc1
  • collect RC feedback on our mailing list
  • create the final release tag
git tag <release_name>
  • create release debian packages
work/packaging/build_debian.sh -release
  • 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
    • echo "master" > ~/branch on ETs account
  • prepare changelog for the third release
  • plan the next release (tickets on savannah)