Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "ETrice/Development/ReleaseCheckList"
< ETrice | Development
m (version in /org.eclipse.etrice.doc/online-doc/config/_master.json) |
(also announce on forum) |
||
Line 33: | Line 33: | ||
** check the availability of [http://www.eclipse.org/etrice/documentation/doc/etrice-doc.html the documentation] | ** check the availability of [http://www.eclipse.org/etrice/documentation/doc/etrice-doc.html the documentation] | ||
** adjust the release date of the [http://projects.eclipse.org/projects/modeling.mdt.etrice/releases/current current release] | ** adjust the release date of the [http://projects.eclipse.org/projects/modeling.mdt.etrice/releases/current current release] | ||
− | ** announce the release on etrice-dev | + | ** announce the release on etrice-dev and eTrice Forum ([https://www.eclipse.org/forums/index.php/f/199/]) |
** check web site contents (look for comments with ''ReleaseCheck'') | ** check web site contents (look for comments with ''ReleaseCheck'') | ||
*** index: marketplace, current Eclipse Installation | *** index: marketplace, current Eclipse Installation |
Revision as of 02:51, 12 November 2019
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
- check whether the version in /org.eclipse.etrice.doc/online-doc/config/_master.json is still appropriate
- 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)
- create an entry in the archived releases section of /etrice/downloads/_index.html
- add the release to /etrice/downloads/_index.html
- remove the old contents of /etrice/documentation/release up to index.php
- 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 and eTrice Forum ([2])
- 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)