Skip to content

Prepare 4.41 development#3854

Merged
HannesWell merged 4 commits into
masterfrom
prepare-R4.41
May 29, 2026
Merged

Prepare 4.41 development#3854
HannesWell merged 4 commits into
masterfrom
prepare-R4.41

Conversation

@eclipse-releng-bot
Copy link
Copy Markdown
Contributor

@eclipse-releng-bot eclipse-releng-bot commented May 29, 2026

Prepare development of Eclipse 4.41.

This includes, but is not limited to:

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

@HannesWell HannesWell merged commit 4d8a77c into master May 29, 2026
11 of 13 checks passed
@HannesWell HannesWell deleted the prepare-R4.41 branch May 29, 2026 20:46
@HannesWell
Copy link
Copy Markdown
Member

HannesWell commented May 29, 2026

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

I've started to automate that task too in

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants