Skip to main content

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.

Jump to: navigation, search

Difference between revisions of "Eclipse 4diac Wiki/Development/4diac Releng"

Line 16: Line 16:
 
#* Tag commit with release (e.g., 1.9.0.M1, 1.10.1)
 
#* Tag commit with release (e.g., 1.9.0.M1, 1.10.1)
 
# Build 4diac-ide
 
# Build 4diac-ide
#* Trigger build in 4diac Hipp instance
+
#* If new release create release dir with sftp (sftp username@build.eclipse.org), e.g., /home/data/httpd/download.eclipse.org/4diac/releases/1.11/4diac-ide
#* Download build results
+
#* Trigger build in 4diac JIPP instance. job 4diac IDE release
#* rename output files according to release: 4diac-ide-incubation_version_platform.ending (e.g., 4diac-ide-incubation_1.9.0.M2_linux.gtk.x86.tar.gz, 4diac-ide-incubation_1.10.1_win32.x86_64.zip)
+
 
# Assemble FORTE
 
# Assemble FORTE
 
#* clone anonymous git :
 
#* clone anonymous git :
 
#* change to release branch
 
#* change to release branch
 
#* zip forte and name it forte-incubation_version.zip
 
#* zip forte and name it forte-incubation_version.zip
# Put it onto eclipse download site
+
#* Put it onto eclipse download site
#* Connect to build.eclipse.org (sftp username@build.eclipse.org)
+
#** Connect to build.eclipse.org (sftp username@build.eclipse.org)
#* go into release dir (e.g., /home/data/httpd/download.eclipse.org/4diac/...)
+
#** go into release dir (e.g., /home/data/httpd/download.eclipse.org/4diac/...)
#* Update release specific update sites
+
#** Update release specific update sites
 
# Update download web site
 
# Update download web site
 
# Prepare news for:
 
# Prepare news for:

Revision as of 16:46, 21 August 2019

Short checklist for 4diac releases:

  1. if minor/major release update version information
    • Update main version info (Manifest, pom):
      • org.eclipse.fordiac.ide
      • org.eclipse.fordiac.product
      • org.eclipse.master
    • For minor releases
      • update any plugins to new version numbers if needed
      • update according features
  2. prepare branding
    • Update splash screen
    • Update update version number in VM Arguments: -Declipse.buildId= (this is needed for AERI)
  3. Prepare git repositories
    • For Major and bug fix releases merge release branch to master
    • Tag commit with release (e.g., 1.9.0.M1, 1.10.1)
  4. Build 4diac-ide
    • If new release create release dir with sftp (sftp username@build.eclipse.org), e.g., /home/data/httpd/download.eclipse.org/4diac/releases/1.11/4diac-ide
    • Trigger build in 4diac JIPP instance. job 4diac IDE release
  5. Assemble FORTE
    • clone anonymous git :
    • change to release branch
    • zip forte and name it forte-incubation_version.zip
    • Put it onto eclipse download site
      • Connect to build.eclipse.org (sftp username@build.eclipse.org)
      • go into release dir (e.g., /home/data/httpd/download.eclipse.org/4diac/...)
      • Update release specific update sites
  6. Update download web site
  7. Prepare news for:
    • 4diac webseite, mirror on sourceforge
  8. Announce it on
    • LinkedIn
    • Xing
    • Google+
    • Researchgate
    • Freshcode

Back to the top