You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Updating the version of the Maven parent, all references to it and the Eclipse products to 4.41
Updating the release version to 4.41 across build scripts
Updating the previous release version to the current Release-Candidate: S-4.40RC2-202605280011
Further tasks:
Review and submit all PRs created in the submodules to prepare them for the new release cycle.
These PRs are all linked to this one.
Review and submit the new N&N pages created for the eclipse website repository.
Submit this PR.
Before the preparation PRs in all submodules have been submitted the build of this change cannot complete (this can still submit it before).
Update build calendar for platform 4.41 release cycle.
After this and all submodule PRs are submitted:
Run the Create Jobs seed job to create the Jenkins jobs of the new stream
Start the new I-build-4.41 job for the first I-build of the new stream
In case the new I-build job is not sufficiently stable, disable it temporarily until it's ready for the usual schedule
As soon as the new I-build is stable, Send the Announcement that the master is open again.
Start the new I-build-4.41 job for the first I-build of the new stream
The new jobs have been created.
But since they will run based on the regular in about one hour, I won't create an manual first run before that.
If that build is successful I'll send the announcement about the reopening of the master tomorrow morning.
Update build calendar for platform 4.41 release cycle.
But at the moment this is mainly awaiting the set up of the corresponding credentials by the IT team (see the linked Gitlab issue). I have some hope that the credentials will be available next week and we can use a modified version of that new code to already create the calendar entries automatically. @MohananRahul can you please hold-off until the end of next week before creating the calendar entries manually?
If the credentials are available until then, I'd like to use the automation already 'now', if it takes longer the entries can still be created by the end of this week.
For the next release preparation, I hope that this will then work entirely automated.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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.
Prepare development of Eclipse 4.41.
This includes, but is not limited to:
4.414.41across build scriptsS-4.40RC2-202605280011Further tasks:
These PRs are all linked to this one.
Before the preparation PRs in all submodules have been submitted the build of this change cannot complete (this can still submit it before).
After this and all submodule PRs are submitted:
Create Jobsseed job to create the Jenkins jobs of the new streamI-build-4.41job for the first I-build of the new streamSend the Announcementthat the master is open again.