Release work for RedDeer 4.7.0 under SimRel 2023-09

This issue is a form of an epic task consisting of all steps that are required to undertake in order to release RedDeer final bits under Eclipse Simultaneous Release 2023-09 which is based on 4.28 platform.

Eclipse Project plan 2023-09 planurl and SimRel release plan simrel. Eclipse API Contract breakages and changes are in porting_guide

Release	Date	Span	Due dates	Notes
2023-09 M1	Friday, July 14, 2023	07/07 to 07/14	Opt-in deadline (new projects only)Create your release record (for new releases)	3 weeks from 2023-06 GA
2023-09 M2	Friday, August 4, 2023	07/28 to 08/04		3 weeks from M1
2023-09 M3	Friday, August 25, 2023	08/18 to 08/25	IP Log submission deadline	3 weeks from M2
2023-09 RC1	Friday, September 1, 2023	08/25 to 09/01	No new features and APIs after this date!Release Review materials dueNew and Noteworthy entries due	1 week from M3
2023-09 RC2	Friday, September 8, 2023	09/01 to 09/09		1 week from RC1
Quiet period	09/08 to 09/12		No builds during "quiet period". It is assumed all code is done by the end of RC2.
2023-09 GA	Wednesday, September 13, 2023		Release reviews conclude on this date	5 days from RC2

Release flow for Eclipse project

General documentation about Eclipse project release engineering relengdocs

Initial changes in new RedDeer release cycle

[x] Upversion to new snapshot version (3.5.0-SNAPSHOT) by M2 mvn org.eclipse.tycho:tycho-versions-plugin:set-version -DnewVersion=3.5.0.qualifier
- [x] In addition, these files need to be upversioned manually: archetype/src/main/resources/archetype-resources/pom.xml archetype/pom.xml
- [x] in pom.xml, change: eclipse-target-site to https://download.eclipse.org/releases/2023-06/, eclipse-orbit-update-site, targetEclipseVersion and any other necessary property.
- [x] Update site/category.xml necessary values
[x] Plan work for new release: issues
[x] Update the PR check job: https://ci.eclipse.org/reddeer/job/reddeer.prcheck/
Update Job config -> Build Triggers -> Trigger Setup
[x] Share the intent to participate in SimRel
- [x] New project release record must be created by M1
- https://projects.eclipse.org/projects/technology.reddeer -> Commiter Tools -> Create a new Release
Create a milestone(s) in release plan
- [x] touch aggrcon file by M2 (org.eclipse.simrel.build - https://git.eclipse.org/c/simrel/org.eclipse.simrel.build.git/)
[x] Next section is only valid if there are breaking changes in IP, features, etc, or one year Release review validity expires (last was done for 2021-06, 2022-06) - need to perform for 2023-06
- [ ] Schedule Release Review after project release is created (1st of 3rd Wed. on each month)
- [ ] This review is pending; contact The Eclipse Management Organization (emo@eclipse.org) to make it public. (can be found under https://projects.eclipse.org/projects/technology.reddeer/releases/3.4.0 -> Review: -> 3.4.0 Release Review link)
- [ ] Request for PMC approval: eclipse technology reddeer -> Committer Tools -> Communication -> Send Email to the PMC)
- [ ] Get +1 on technology-pmc mailing list request: [pmc approval]
- [ ] (Outdated) Create IP Log (https://dev.eclipse.org/ipzilla): eclipse technology reddeer -> Committer Tools -> Intelectual Property -> Generate IP log
- [ ] (Outdated) IP log: [iplog]
- [ ] Wait for release review is done on planned date after all above steps are fulfilled (mb merge with next step)
- [ ] Gitlab issue for [release review] with approval
- [ ] (Outdated) Link CQs if there are any: see [iplog]
[x] Jump in SimRel Milestone release with offset +3 (mb rewrite somehow, is not clear) this is probably M2 +3 as reddeer cannot be built unless we got full stack of packages in some update site and this is usually happening at the end of M1.
[x] RedDeer milestone releasing - MX, RCX, Final, includes:
Implement features, bug fixes, etc.
Release proper milestone via RedDeer Jenkins CI
Create Eclipse SimRel aggregation build repo gerrit commit, validate - https://ci.eclipse.org/simrel/job/simrel.runaggregator.VALIDATE.gerrit/, push, see "SubTasks" section.
[x] Do final release milestone
[x] Triage issues for next release, close, move, etc.
[x] Create new release tag in reddeer repository and upload artifacts using github-project-automation scripts (tag is created if it does not exist)
[x] Spread release note to proper mailing lists (reddeer-dev, devtools-team)
[x] Create new milestone on github
[x] Close old milestone

SubTasks:

Creating gerrit commit to Eclipse Simrel aggregation build repo

requires signed ECA, and Eclipse user account
Resources: https://wiki.eclipse.org/Simrel/Contributing_to_Simrel_Aggregation_Build, https://wiki.eclipse.org/Gerrit
Git repo address: git clone https://git.eclipse.org/r/simrel/org.eclipse.simrel.build
Add repo locally into IDE via Git perspective
Open simrel repo properties - Configuration -> setup those branch.master.remote=origin, branch.master.merge=refs/heads/master and branch.master.rebase=true
(Optional) Install the CBI p2Repo Aggregator - http://download.eclipse.org/cbi/updates/aggregator/ide/4.8
make changes to particular aggrcon file (reddeer.aggrcon)
Test build locally: Aggregation (only) from Eclipse IDE and CBI aggregator From the aggregation editor, right-click on the aggregation model and run Clean then Build Aggregation. See CBI/aggregator/manual#Global_actions OR in the repo with cli, run mvn clean verify
Stage changes, create commit message with change ID attached (signoff as well)
Commit and push... (push with CLI: git push origin HEAD:refs/for/master)
When pushing commit into gerrit repo over HTTPS, use passphrase that can be get while being logged here: https://git.eclipse.org/r/#/settings/http-password
Gerrit commit created, validation jenkins job started: https://ci.eclipse.org/simrel/job/simrel.runaggregator.VALIDATE.gerrit/
If all good, job will add +1 to the gerrit commit, one needs to get another +2 from someone who has right to push into repo
push to repo

Create and push github tag

Merge Upversion PR
Create an annotated (ideally) tag aiming proper Eclipse Milestone where RedDeer milestone bits will be included
git tag -a <tagname>
write a brief description
check tag's head commit git show <tagname>
push tag into origin git push --tags
push tag into upstream git push upstream --tags

Creating a milestone

Create milestone tag (see above)
Run https://ci.eclipse.org/reddeer/job/reddeer.milestone/ and set REDDEER_TAG to <tagname>
Pass empty string into BUILD_ALIAS as we stopped using build aliases
Create a gerrit commit on org.eclipse.simrel.build repo, see (#gerrit)

Creating a final milestone / release

Create final milestone tag (see above)
Run https://ci.eclipse.org/reddeer/job/reddeer.releases/ and set REDDEER_TAG to <tagname>
Set proper REDDEER_UPDATE_SITE (ie. 2.7.0)
Create a gerrit commit on org.eclipse.simrel.build repo, see (#gerrit)

[iplog]: [pmc approval]: [release review]:

eclipse / reddeer