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.
Eclipse 4diac Wiki/Development/4diac Releng
Short checklist for 4diac releases:
- 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
- Update main version info (Manifest, pom):
- prepare branding
- Update splash screen
- Update update version number in VM Arguments: -Declipse.buildId= (this is needed for AERI)
- 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)
- Build 4diac-ide
- Trigger build in 4diac Hipp instance
- Download build results
- 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
- 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
- Update download web site
- Prepare news for:
- 4diac webseite, mirror on sourceforge
- Announce it on
- Google+
- Researchgate
- Freshcode