Hi Hans, I think this is a great idea. I'll be filing small UI bugs that I think still need addressing, like issue #6438 (in apache/hop). It would be great if you all could file others. I'll do my best to fix them. Let's spend the next couple of weeks ironing out the smaller kinks. All in all though... 2.17 looks amazing.
Cheers, Matt Op wo 21 jan 2026 om 10:39 schreef Hans Van Akelyen < [email protected]>: > Hi All, > > Our next release, 2.17 is coming up soon, and it is looking to be one of > our largest releases since joining the ASF [1]. > I would like to thank everyone that has worked on this release. > > With the release approaching I propose we slow down the phase where we > merge new code. > Except for very annoying bugs, regressions, CVE's we should consider our > current codebase as the next release. > This will give everyone the time to give it some final tests before we > start building the Release Candidate. > > As this is a massive release with many changes I will start drafting the > release blog post and give everyone time to review this and add their own > changes they want to highlight. > > The final cutoff date for this release will be 30/01 and the release will > be created and voted on in the first week of February. > > Cheers, > Hans > > [1] > https://github.com/apache/hop/issues?q=state%3Aclosed%20milestone%3A%222.17%22 > > >
