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.
Difference between revisions of "Eclipse 4diac Wiki/Development/4diac Releng"
| (2 intermediate revisions by the same user not shown) | |||
| Line 11: | Line 11: | ||
# prepare branding | # prepare branding | ||
#* Update splash screen | #* Update splash screen | ||
| − | #* | + | #* For major release change p2.inf from milestone update site to latest release update site: download.eclipse.org/4diac/updates/latest,name:Eclipse 4diac Latest Release |
# update whats new section | # update whats new section | ||
# Prepare git repositories | # Prepare git repositories | ||
| Line 29: | Line 29: | ||
# Update download page | # Update download page | ||
# Move files from previouse release to http://archive.eclipse.org | # Move files from previouse release to http://archive.eclipse.org | ||
| + | #* Location: /home/data/httpd/archive.eclipse.org/4diac/releases/ | ||
#* For more information see [[IT Infrastructure Doc#Move files to archive.eclipse.org?]] | #* For more information see [[IT Infrastructure Doc#Move files to archive.eclipse.org?]] | ||
#* As we are using the mirror link script in our download page no changes to the download page are needed | #* As we are using the mirror link script in our download page no changes to the download page are needed | ||
| Line 46: | Line 47: | ||
== Start the Feature Freeze Phase == | == Start the Feature Freeze Phase == | ||
# Create dedicated branches for the maintenance of the release (e.g., 1.15.x) | # Create dedicated branches for the maintenance of the release (e.g., 1.15.x) | ||
| + | #* push them to git with: git push origin HEAD:1.15.x | ||
| + | #*THE FOLLOWING SHOULD NOT BE NEEDED ANYMORE: | ||
# Create CI jobs both for the 4diac-IDE and FORTE. Each component needs 2 jobs, one triggered at each commit, and the other for the nightly build. The procedure is similar so only the 4diac-IDE will be shown as an example. | # Create CI jobs both for the 4diac-IDE and FORTE. Each component needs 2 jobs, one triggered at each commit, and the other for the nightly build. The procedure is similar so only the 4diac-IDE will be shown as an example. | ||
#* Go to [https://hudson.eclipse.org/4diac/ Jenkins] | #* Go to [https://hudson.eclipse.org/4diac/ Jenkins] | ||
Revision as of 17:04, 1 March 2021
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
- For major release change p2.inf from milestone update site to latest release update site: download.eclipse.org/4diac/updates/latest,name:Eclipse 4diac Latest Release
- update whats new section
- 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)
- Push tag to gerrit: git push origin 1.11.0 HEAD:refs/heads/1.11.x
- Build 4diac-ide
- Trigger build in 4diac JIPP instance. job 4diac IDE release
- 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 page
- Move files from previouse release to http://archive.eclipse.org
- Location: /home/data/httpd/archive.eclipse.org/4diac/releases/
- For more information see IT Infrastructure Doc#Move files to archive.eclipse.org?
- As we are using the mirror link script in our download page no changes to the download page are needed
- Prepare news for:
- 4diac web page, mirror on sourceforge
- Announce it on
- Google+
- Researchgate
- Freshcode
- iot mailing list
- 4diac dev mailing list
Start the Feature Freeze Phase
- Create dedicated branches for the maintenance of the release (e.g., 1.15.x)
- push them to git with: git push origin HEAD:1.15.x
- THE FOLLOWING SHOULD NOT BE NEEDED ANYMORE:
- Create CI jobs both for the 4diac-IDE and FORTE. Each component needs 2 jobs, one triggered at each commit, and the other for the nightly build. The procedure is similar so only the 4diac-IDE will be shown as an example.
- Go to Jenkins
- On the left menu, click on New Item, and then select the option "Copy from" and type the name of the previous version (for example "4diac IDE 1.10.x", and "4diac IDE 1.11.x Gerrit")
- On the new job, you need to change the last version to the current one (for example 1.10.x to 1.11.x) in the following places:
- General -> Description
- Source-Code-Management -> Branches to build
- And for the gerrit one, also the following:
- General -> This Build is parametrized -> Text-Parameter -> Default Value (Vorgabewert)
- Gerrit Trigger -> Dynamic Trigger Configuration -> Branches -> Pattern