Skip to main content

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.

Jump to: navigation, search

Eclipse 4diac Wiki/Development/4diac Releng

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