ETrice/Development/ReleaseCheckList
< ETrice | Development
Revision as of 09:55, 11 October 2019 by Unnamed Poltroon (Talk) (Remove obsolete steps in release process)
Release Check List
Release Time Line
- week -3
- check for potential bundles without CQ (deprecated)
- retrieve all project dependencies using Maven:
mvn dependency:tree > dependency_tree.txt. There is a manually triggered Jenkins job for this purpose. - manually check for missing CQs
- create new (most often piggy back) CQs using the PMI
- submit IP logfor approval
- week -2
- prepare review documentation
- you have to log on as a committer
- then go to [1]
- press Edit
- and change to the Review Documentation tab
- send a link to the review documentation to the modeling-pmc mailing list
- wait for +1 of pmc
- forward it to emo
- prepare review documentation
- week -0
- iterate
- Test of Release Candidate
- fix and push
- final Test of Release Candidate
- tag the release and start a build
- edit the eTrice web page (available from Git)
- add the release to /etrice/pages/_download.html
- add a note to /etrice/pages/_index.html
- remove the old contents of /etrice/documentation/doc
- copy the current HTML contents including images to this doc folder
- push the eTrice web site
- check the availability of the documentation
- adjust the release date of the current release
- announce the release on etrice-dev
- check web site contents (look for comments with ReleaseCheck)
- index: marketplace, current Eclipse Installation
- download: check the links, check versions, current release (first heading), market place
- update eTrice market place
- update https://projects.eclipse.org/projects/modeling.mdt.etrice (download link)
- iterate