Difference between revisions of "Release Checklist"
Jump to navigation
Jump to search
| Line 8: | Line 8: | ||
git branch bell |
git branch bell |
||
* remove all tools and libraries which are not sufficiently mature to be included in the release |
* 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 |
||
| + | wrappers: cairo, database/postgresql, ewlc, llvm, ??? |
||
* switch ET to use the new branch |
* switch ET to use the new branch |
||
* create release candidate |
* create release candidate |
||
Revision as of 22:02, 24 January 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 branch for the next release
git branch 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 wrappers: cairo, database/postgresql, ewlc, llvm, ???
- 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)