Release work for RedDeer NEXT under SimRel 2022-12

[odockal]

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 2022-12 which is based on 4.26 platform.

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

Release	Date	Span	Due dates	Notes
2022-12 M1	Friday, October 07, 2022	09/30 to 10/07	Opt-in deadline (new projects only) Create your release record (for new releases)	2 weeks from 2022-09 GA
2022-12 M2	Friday, October 28, 2022	10/21 to 10/28		3 weeks from M1
2022-12 M3	Friday, November 18, 2022	11/11 to 11/18	IP Log submission deadline	3 weeks from M2
2022-12 RC1	Friday, November 25, 2022	11/18 to 11/25	No new features and APIs after this date! Release Review materials due New and Noteworthy entries due	1 week from M3
2022-12 RC2	Friday, December 2, 2022	11/25 to 12/02		1 week from RC1
Quiet period	12/02 to 12/06		No builds during "quiet period". It is assumed all code is done by the end of RC2.
2022-12 GA	Wednesday, December 07, 2022		Release reviews conclude on this date	5 days from RC2

Release flow for Eclipse project

• [] Upversion to proper snapshot version (3.5.0-SNAPSHOT) if not done yet

• mvn org.eclipse.tycho:tycho-versions-plugin:set-version -DnewVersion=3.5.0.qualifier

• In addition, these files were modified manually:

• archetype/src/main/resources/archetype-resources/pom.xml

• archetype/pom.xml

• [x] Plan work for new release: issues

• [x] Update the PR check job: https://ci.eclipse.org/reddeer/job/reddeer.prcheck/

• [x] Share the intent to participate in SimRel

• • [x] New project release record must be created by M1
• • [x] touch aggrcon file by M2

• [x] Creating new project release

• https://projects.eclipse.org/projects/technology.reddeer -> Commiter Tools -> Create a new Release

• • [x] Create a milestone(s) in release plan

• 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)
• • [ ] Check if there is existing release review approved already, approval would last for whole year so there is no need for review or each milestone!
• • [ ] 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]
• • [ ] Create IP Log (https://dev.eclipse.org/ipzilla): eclipse technology reddeer -> Committer Tools -> Intelectual Property -> Generate IP log
• • [ ] IP log: [iplog]
• • [ ] Wait for release review is done on planned date after all above steps are fulfilled
• • [ ] Gitlab issue for [release review] with approval
• • [ ] Link CQs if there are any: see [iplog]
• • [ ] Do final release milestone

• [x] Jump in SimRel Milestone release with offset +3 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 changes, fixes, etc. to RD

• Release proper milestone via https://ci.eclipse.org/reddeer CCI

• Create Eclipse SimRel aggregation build repo gerrit commit, validate - https://ci.eclipse.org/simrel/job/simrel.photon.runaggregator.VALIDATE.gerrit/, push, see sub-tasks.

• [x] Create new release tag in reddeer repository and upload artifacts using github-project-automation scripts

• [x] Spread release note to proper mailing lists (reddeer-dev)

• [x] Triage issues for next release, close, move, etc.

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 cli, run mvn clean verify
• Stage changes, create commit message with change ID attached (signoff as well)
• Commit and push...
• 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.photon.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

• 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]: