Difference between revisions of "Release Checklist"
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 |
||
| + | git branch bell |
||
| + | * remove all tools and libraries which are not sufficiently mature to be included in the release |
||
| + | * switch ET to use the new branch |
||
* create release candidate |
* create release candidate |
||
git tag <release_name>-rc1 |
git tag <release_name>-rc1 |
||
| Line 14: | Line 18: | ||
* create tarball and put on FTP server |
* create tarball and put on FTP server |
||
* 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 |
||
* plan the next release (tickets on savannah) |
* plan the next release (tickets on savannah) |
||
Revision as of 22:00, 14 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
- 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)