Having gone through the release process a few times myself, I think we should rotate the Release Manager role between releases, not to create concentrated knowledge.
Sorry to be speaking for Kennedy here, but he has been in vacation for a few weeks now and should be back before the end of the month. On Tue, Nov 18, 2025 at 12:08 Alex Porcelli <[email protected]> wrote: > Thank you for sharing this update, and I am really sorry to hear about > your situation. This is a challenging moment, especially so close to > the holidays. Please let me know if there is anything I can do to > support you during this transition. Your work and commitment to the > project have always been greatly appreciated. > > Regarding the 10.2 release, given the circumstances and the fact that > we have not heard from Kennedy recently, I propose that Eduardo and I > take over as Release Managers. We will be very happy to collaborate > with Kennedy if he is still planning to participate. > > At this point, it is not realistic to aim for a December timeline, but > before proposing a new one, the priority is to get release management > in place. > > Thank you again for the transparency, Jason. Wishing you the very best > of luck in the coming weeks. Please take care and feel free to reach > out if you need any support. > > - > Alex > > On Tue, Nov 18, 2025 at 11:57 AM Jason Porter <[email protected]> > wrote: > > > > Hello everyone, > > > > I know you are all busy and eagerly waiting for the 10.2 release. I wish > I had better news about this. Two weeks ago, I was notified that I am being > RIF'd (Reduction In Force) from IBM in early December. Due to this > unforeseen issue, my work on the release has taken a back burner to me > looking for another job. I've been trying to up skill, rework my resume, as > well as interviewing and applying to positions. > > > > This will mean that the release will end up slipping from the initial > timeline. At this point, I'm not sure when the release will come out. For > those interested in helping, I've been testing the build in my own > workspace in Jenkins. You can do the same at > https://ci-builds.apache.org/job/KIE/job/__dev/. You should be able to > log in to the Jenkins cluster (using your Apache credentials) and create > your own folder at that link. It may be easiest to copy the 0-seed-job > either from my folder or from the main builds. You'll want to modify where > it points, which branches to use, etc. More can be read about how these are > all put together at > https://github.com/apache/incubator-kie-kogito-pipelines/blob/main/docs/jenkins.md > (and associated md files). I'm certainly available to answer questions, but > for now my focus is elsewhere. > > > > -- > > > > Jason Porter > > Software Engineer > > He/Him/His > > > > IBM > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
