Release work for RedDeer 3.1.0 milestone under Eclipse 2020-09

[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 2020-06.

Eclipse Project plan 2020-09 planurl and SimRel release plan link.

Release | Date | Span | Due dates | Notes

Release flow for Eclipse project

• Upversion to proper snapshot version (3.1.0-SNAPSHOT) if not done yet

• mvn org.eclipse.tycho:tycho-versions-plugin:set-version -DnewVersion=3.1.0.qualifier
• In addition, these files were modified manually:
• archetype/src/main/resources/archetype-resources/pom.xml
• archetype/pom.xml

• Plan work for new release: issues
• Create new PR check job (2020-06) by copying and updating reddeer.prcheck.2020-09
• Share the intent to participate in SimRel

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

• Creating new project release

• https://projects.eclipse.org/projects/technology.reddeer -> Commiter Tools -> Create a new Release
• • 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 2020-03, so until 2021-03 we are ok)
• • 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/2.9.0 -> Review: -> 2.9.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
• • Bugzilla for [release review] with approval
• • Link CQs if there are any: see [iplog]
• • Do final release milestone

• 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.
• 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.

• Spread release note to proper mailing lists (reddeer-dev)
• Create new release tag in reddeer repository and upload artifacts using [github-project-automation] scripts
• 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]:
[github-project-automation]: https://github.com/odockal/github-project-automation