Skip to main content
Jump to: navigation, search

Difference between revisions of "ETrice/Development/ReleaseCheckList"

(Release Time Line)
(some updates wrt CQs and release reviews)
 
(21 intermediate revisions by 2 users not shown)
Line 4: Line 4:
  
 
* week -3
 
* week -3
** submit [http://www.eclipse.org/projects/ip_log.php?projectid=modeling.mdt.etrice IP log] for approval
+
** 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.
** [http://eclipse.org/projects/tools/downloads.php?id=modeling.mdt.etrice check for potential bundles without CQ]
+
** 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
 +
** 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 (''this is necessary only once per year with a full review'')
 
* week -2
 
* week -2
 
** prepare review documentation
 
** prepare review documentation
 
*** you have to log on as a committer
 
*** you have to log on as a committer
*** then go to [http://projects.eclipse.org/projects/release/0.3.0-3#]
+
*** then go to the [http://projects.eclipse.org/projects/release/0.3.0-3# release review page]
 
*** 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 [emo@eclipse.org emo]
+
*** wait for +1 of pmc
* week-0
+
*** forward it to [mailto://emo@eclipse.org emo]
** do some final testing
+
* week -0
** make sure the Eclipse Help is working
+
** check whether the version in /org.eclipse.etrice.doc/online-doc/config/_master.json is still appropriate
** push everything
+
** iterate
** start a build with site signing checked and release version (e.g. 0.3.0) and build type R
+
*** [[ETrice/Test of Release Candidate|Test of Release Candidate]]
** test the newly created nightly build using a current plain modeling package of Eclipse
+
*** fix and push
** log in to the eclipse server
+
** final [[ETrice/Test of Release Candidate|Test of Release Candidate]]
** copy the nightly build to updates and archives
+
** tag the release and start a build
 
** edit the eTrice web page ([http://git.eclipse.org/c/www.eclipse.org/etrice.git/ available from Git])
 
** edit the eTrice web page ([http://git.eclipse.org/c/www.eclipse.org/etrice.git/ available from Git])
*** add the release to /etrice/pages/_download.html
+
*** create an entry in the archived releases section of /etrice/downloads/_index.html
*** add a note to /etrice/pages/_index.html
+
*** add the release to /etrice/downloads/_index.html
*** remove the old contents of /etrice/documentation/doc
+
*** remove the old contents of /etrice/documentation/release ''up to index.php''
 
*** copy the current HTML contents including images to this doc folder
 
*** copy the current HTML contents including images to this doc folder
 
** push the eTrice web site
 
** push the eTrice web site
 
** 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]
** tag the release
 
 
** 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 [https://www.eclipse.org/forums/index.php/f/199/ 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 [https://marketplace.eclipse.org/content/etrice eTrice market place]
 +
** update https://projects.eclipse.org/projects/modeling.mdt.etrice (download link)
  
 
== Other Resources of Information ==
 
== Other Resources of Information ==

Latest revision as of 02: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)
  • 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
  • week -0
    • check whether the version in /org.eclipse.etrice.doc/online-doc/config/_master.json is still appropriate
    • iterate
    • 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)

Other Resources of Information

Back to the top