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
[x] Upversion to proper snapshot version (3.1.0-SNAPSHOT) if not done yet
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!
[ ] 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]
[x] 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.
Open simrel repo properties - Configuration -> setup those branch.master.remote=origin, branch.master.merge=refs/heads/master and branch.master.rebase=true
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)
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
[x] 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
[x] Plan work for new release: issues
[x] Create new PR check job (2020-06) by copying and updating reddeer.prcheck.2020-09
[x] Share the intent to participate in SimRel
[x] Creating new project release
https://projects.eclipse.org/projects/technology.reddeer -> Commiter Tools -> Create a new Release
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)
[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] Spread release note to proper mailing lists (reddeer-dev)
[x] Create new release tag in reddeer repository and upload artifacts using github-project-automation scripts
[x] Triage issues for next release, close, move, etc.
SubTasks:
Creating gerrit commit to Eclipse Simrel aggregation build repo
Create and push github tag
git tag -a <tagname>git show <tagname>git push --tagsgit push upstream --tagsCreating a milestone
<tagname>Creating a final milestone / release
<tagname>[iplog]: [pmc approval]: [release review]: