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
(use Maven to retrieve dependencies) |
(CQs) |
||
Line 5: | Line 5: | ||
* week -3 | * week -3 | ||
** [http://eclipse.org/projects/tools/downloads.php?id=modeling.mdt.etrice check for potential bundles without CQ (deprecated)] | ** [http://eclipse.org/projects/tools/downloads.php?id=modeling.mdt.etrice check for potential bundles without CQ (deprecated)] | ||
− | ** retrieve all project dependencies using Maven: <code>mvn dependency:tree > dependency_tree.txt</code> | + | ** 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 |
** 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] | ||
** submit [https://projects.eclipse.org/projects/modeling.mdt.etrice/iplog/project IP log]for approval | ** submit [https://projects.eclipse.org/projects/modeling.mdt.etrice/iplog/project IP log]for approval | ||
* week -2 | * week -2 |
Revision as of 06:34, 10 August 2018
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
- replace all version strings (using e.g. Notepad++ because not all files are in the Workspace)
- MANIFEST.MF
- for dependencies in manifests search regex org\.eclipse\.etrice(.*)"1.1.1" and replace with org.eclipse.etrice\1"1.1.2"
- feature.xml
- category.xml
- pom.xml
- MANIFEST.MF
- 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 (using e.g. Notepad++ because not all files are in the Workspace)