Notice: This Wiki is now read only and edits are no longer 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 (→Release Time Line) |
m (→Release Time Line) |
||
Line 16: | Line 16: | ||
** forward it to [mailto://emo@eclipse.org emo] | ** forward it to [mailto://emo@eclipse.org emo] | ||
* week -0 | * week -0 | ||
− | ** replace all version strings in MANIFEST.MF and pom.xml (using e.g. Notepad++ because not all files are in the Workspace) | + | ** replace all version strings in MANIFEST.MF, feature.xml and pom.xml (using e.g. Notepad++ because not all files are in the Workspace) |
+ | *** for dependencies in manifests search regex org\.eclipse\.etrice(.*)"1.1.1" and replace with org.eclipse.etrice\1"1.1.2" | ||
** iterate | ** iterate | ||
*** [[ETrice/Test of Release Candidate|Test of Release Candidate]] | *** [[ETrice/Test of Release Candidate|Test of Release Candidate]] |
Revision as of 07:06, 9 February 2018
Release Check List
Release Time Line
- week -3
- submit IP logfor approval
- check for potential bundles without CQ
- 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
- replace all version strings in MANIFEST.MF, feature.xml and pom.xml (using e.g. Notepad++ because not all files are in the Workspace)
- for dependencies in manifests search regex org\.eclipse\.etrice(.*)"1.1.1" and replace with org.eclipse.etrice\1"1.1.2"
- iterate
- Test of Release Candidate
- fix and push
- start a build with site signing checked and release version (e.g. 0.3.0) and build type R
- final Test of Release Candidate
- log in to the eclipse server (PuTTY <user>@build.eclipse.org - you will be logged out after first login. Wait for automatic confirmation mail and reply. Then login again.)
- copy the nightly build to updates and archives
- 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
- tag the release
- 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)
- replace all version strings in MANIFEST.MF, feature.xml and pom.xml (using e.g. Notepad++ because not all files are in the Workspace)