eclipse
4.18 Releng
Tracks the release engineering activities for the 4.18 release.
Opening actions
- [x] Update version numbers
- [X] Create Milestone 4.19 in Github
- [X] Move 4.17 open issues to 4.18
- [X] Create Release in Project Administration
Release day - 7
- [ ] Announce new release pending in discussions
- [ ] Revisit all open tasks
Release day
- [ ] Create Github release (Creates Tag and Announcement in Discussions)
- [ ] Update README.MD
- [ ] Update 4.18 Release in Project Administration
- [ ] Create 4.19 Release in Project Administration
- [ ] Move 4.18 open issues to 4.19
@speckyspooky @wimjongman
I'd like to do a first milestone build so that the generated Oomph products show a release choice as well as two choices for 4.18 versions:
I've tested installer with the 4.17 release and with the 4.18 nightly build; both can create a simple report that previews in the tab and in the browser. So I'm quite sure the current nightly build for 4.18 is in good shape before we make substantial changes.
I assume you're both okay with this, but if not speak out!
@merks Hi Ed, today I synchronised my fork with the small PRs from milestone 4.18 and Tycho 4.0.9. After the rebuild I have 51 errors on my project based on a problem "org.mozilla.rhino_1.17.15.jar". By default it is comming from orbit so I'm confused abot the errors.
I tried the following steps to solve the problem (currently without success):
- Perform Setup Task
- Restart eclipse
- Project, Clean up
- Restart eclipse
O had this issue in the past and these steps had success but not this time. Have you an idea for that why the rhino-library should'n be loaded correctly...?
Screen of "Perform Setup Task"
Screen of "Errors"
@merks Hi Ed, now it is solved. I figured out that the first build after the update creates lot of .classpath-files. I removed all with the header revision and afterwards all references are fine. I thought the "clean up" will do it but good news now I have not longer erros.
This looks fine for me too:
And it should be fine because the re-export from core should properly make things visible. Perhaps a PDE glitching with the target platform...
@hvbtup
Can I delete this branch now? I think it's been merged, right?
https://github.com/eclipse-birt/birt/tree/tagged-pdf
FYI, I've produced the following milestone build:
https://download.eclipse.org/birt/updates/milestone/S202411301317
This is a potential release candidate. Please test it and help fix any problems that need to be addressed before we promote the 4.18 release. Ideally we would release on or shortly after December 4th.
@wimjongman @speckyspooky @hvbtup
Guys, should I assume that the release candidate is ready to be released? I.e., no further manual testing and no further explicit confirmation is pending or required? (The rest of SimRel will release tomorrow.)
I'm happy if we can release any time this week late Wednesday or onward. The EPP packages are made visible at 9:30AM EST but we can have our own deadline.
I started testing and I figured out an issue which is a release blocker for BIRT 4.18 OSGi version - #1992 .
@merks The new issue of OSGi seems to be based on missing dependency "org.apache.commons.logging.LogFactory". Have you an idea for that?
I have tested BIRT runtime, runtime OSGi and IDE based on windows 11. All tests are successfuly based on the latest build N202412041727.
I used for the integrated web applicaton server tests Tomcat 9.0.78, 89, 93.
There's a new release candidate
https://download.eclipse.org/birt/updates/milestone/S202412041951
It should be the same content asN202412041727.
The release is available:
https://download.eclipse.org/birt/updates/release/4.18.0
We are done here. Next stop: 4.19 (#1997)
@merks @hvbtup @speckyspooky My sincere thanks for sticking with the project and making progress every time. Your expertise is truly top class and it is a pleasure to work with you.