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
(some updates wrt CQs and release reviews) |
|||
Line 4: | Line 4: | ||
* week -3 | * week -3 | ||
− | |||
** retrieve all project dependencies using Maven: <code>mvn dependency:tree > dependency_tree.txt</code>. There is a manually triggered [https://ci.eclipse.org/etrice/job/dependencies/ Jenkins job] for this purpose. | ** retrieve all project dependencies using Maven: <code>mvn dependency:tree > dependency_tree.txt</code>. There is a manually triggered [https://ci.eclipse.org/etrice/job/dependencies/ Jenkins job] for this purpose. | ||
+ | ** download the job's ''complete'' log and execute in a bash: <code>grep -E "\+\-|\\\\-" log.txt | grep -v "org.eclipse" | sed -e 's/\\-/\+\-/g' | sort -u</code> | ||
** manually check for missing CQs | ** manually check for missing CQs | ||
** create new (most often piggy back) CQs using the [https://projects.eclipse.org/projects/modeling.mdt.etrice/cq/create PMI] | ** create new (most often piggy back) CQs using the [https://projects.eclipse.org/projects/modeling.mdt.etrice/cq/create PMI] | ||
− | ** submit [https://projects.eclipse.org/projects/modeling.mdt.etrice/generate-iplog/project IP log]for approval | + | ** submit [https://projects.eclipse.org/projects/modeling.mdt.etrice/generate-iplog/project IP log]for approval (''this is necessary only once per year with a full review'') |
* week -2 | * week -2 | ||
** prepare review documentation | ** prepare review documentation | ||
Line 15: | Line 15: | ||
*** press ''Edit'' | *** press ''Edit'' | ||
*** and change to the ''Review Documentation'' tab | *** and change to the ''Review Documentation'' tab | ||
− | ** send a link to the review documentation to the [mailto://modeling-pmc@eclipse.org modeling-pmc mailing list] | + | ** ''this is necessary only once per year with a full review'' |
− | ** wait for +1 of pmc | + | *** send a link to the review documentation to the [mailto://modeling-pmc@eclipse.org modeling-pmc mailing list] |
− | ** forward it to [mailto://emo@eclipse.org emo] | + | *** wait for +1 of pmc |
+ | *** forward it to [mailto://emo@eclipse.org emo] | ||
* week -0 | * week -0 | ||
** check whether the version in /org.eclipse.etrice.doc/online-doc/config/_master.json is still appropriate | ** check whether the version in /org.eclipse.etrice.doc/online-doc/config/_master.json is still appropriate |
Revision as of 03:33, 4 December 2019
Release Check List
Release Time Line
- week -3
- retrieve all project dependencies using Maven:
mvn dependency:tree > dependency_tree.txt
. There is a manually triggered Jenkins job for this purpose. - download the job's complete log and execute in a bash:
grep -E "\+\-|\\\\-" log.txt | grep -v "org.eclipse" | sed -e 's/\\-/\+\-/g' | sort -u
- manually check for missing CQs
- create new (most often piggy back) CQs using the PMI
- submit IP logfor approval (this is necessary only once per year with a full review)
- retrieve all project dependencies using Maven:
- week -2
- prepare review documentation
- you have to log on as a committer
- then go to the release review page
- press Edit
- and change to the Review Documentation tab
- this is necessary only once per year with a full review
- 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
- 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)