Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The value of
<M2E_RELEASE>
is2.7.0
.The value of
<M2E_PREVIOUS_RELEASE>
is2.6.2
and the value of<M2E_RELEASE_WO_DOTS>
is270
The value of
<CONTAINING_SIMREL>
is2024-12
Release process steps:
RELEASE_NOTES.md
dedicated to this release (done with this PR).m2e-promote-snapshots-to-release
M2E Jenkins job with parameterreleaseVersion
value<M2E_RELEASE>
https://git.eclipse.org/c/simrel/org.eclipse.simrel.build.git/tree/m2e.aggrcon, usually it is sufficient to update the repo URL and description.
<M2E_RELEASE>
on the release commit (usually this PR's commit).Create a new Release
at the M2E project website: https://projects.eclipse.org/projects/technology.m2eName: <M2E_RELEASE>, Release date: default is today, which is usually fine.
In the
Review Documentation
section add theNew & Notworthy URL
:https://github.com/eclipse-m2e/m2e-core/blob/master/RELEASE_NOTES.md#<M2E_RELEASE_WO_DOTS>
<M2E_RELEASE>-tag