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-03 which is based on 4.27 platform.
Eclipse Project plan 2023-03 planurl and SimRel release plan simrel. Eclipse API Contract breakages and changes are in porting_guide
Release
Date
Span
Due dates
Notes
2023-03 M1
Friday, January 13, 2023
01/06 to 01/13
Opt-in deadline (new projects only) Create your release record (for new releases)
4 weeks from 2022-12 GA
--
--
--
--
--
2023-03 M2
Friday, February 3, 2023
01/27 to 02/03
3 weeks from M1
2023-03 M3
Friday, February 24, 2023
02/17 to 02/24
IP Log submission deadline
3 weeks from M2
2023-03 RC1
Friday, March 3, 2023
02/24 to 03/03
No new features and APIs after this date! Release Review materials due New and Noteworthy entries due
1 week from M3
2023-03 RC2
Friday, March 10, 2023
03/03 to 03/10
1 week from RC1
Quiet period
03/10 to 03/14
No builds during "quiet period". It is assumed all code is done by the end of RC2.
2023-03 GA
Wednesday, March 15 2023
Release reviews conclude on this date
5 days from RC2
Release flow for Eclipse project
General documentation about Eclipse project release engineering releng_docs
[x] Upversion to new snapshot version (3.5.0-SNAPSHOT)
mvn org.eclipse.tycho:tycho-versions-plugin:set-version -DnewVersion=3.5.0.qualifier
In addition, these files need to be upversioned manually:
archetype/src/main/resources/archetype-resources/pom.xmlarchetype/pom.xml
[ ] 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!
[ ] 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]
[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 2023-03 which is based on 4.27 platform.
Eclipse Project plan 2023-03 planurl and SimRel release plan simrel. Eclipse API Contract breakages and changes are in porting_guide
Release flow for Eclipse project
General documentation about Eclipse project release engineering releng_docs
[x] Upversion to new snapshot version (3.5.0-SNAPSHOT)
mvn org.eclipse.tycho:tycho-versions-plugin:set-version -DnewVersion=3.5.0.qualifierIn addition, these files need to be upversioned manually:
archetype/src/main/resources/archetype-resources/pom.xmlarchetype/pom.xml[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] 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 2021-06, 2022-06) - need to perform for 2023-06
[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 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.photon.runaggregator.VALIDATE.gerrit/, push, see sub-tasks.
[x] Do final release milestone
[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] Triage issues for next release, close, move, etc.
[x] Close old milestone
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]: