Thanks for the context and for sharing the references. Regarding the release procedure, I agree the existing document seems fairly comprehensive. The sync PR you mentioned is helpful, and I’m happy to get that merged as soon as possible. I also have a similar PR open for drools [1]. When you have a moment, I’d appreciate your review there as well.
Once both of those are merged, my plan is to do a dry run following Automation D from the release document, using the main branch. This should give us a clear signal on whether the pipelines are running smoothly and are ready to proceed once the GWT-related work is completed. Regarding the GWT removal, the work is planned and split into three PRs to keep the changes manageable: Create the new BPMN Editor–related packages (PR #1) — targeted to be ready by EOY Adapt the codebase to depend only on the new BPMN/DMN/SceSim Editors (PR #2) Remove the classic BPMN/DMN/SceSim Editor packages (PR #3) Once PR #1 is in and the dry run is complete, I can share an updated status and a clearer view of what remains before we can formally kick off the release process. Thanks again for the offer to help, much appreciated! [1] https://github.com/apache/incubator-kie-drools/pull/6507 On 2025/12/10 14:18:18 Alex Porcelli wrote: > Thanks for the update, and welcome back. As you insist on continuing > as Release Manager for 10.2, that is fine with me. My primary concern > has been the timeline. Given the gap over the past few weeks and the > outstanding blockers you mentioned, the schedule is already impacted, > so it would be helpful to get an updated view of where things stand. > Since some critical items are still pending, this might also be a good > moment to share the latest status so we all know what remains before > we can start the release process. > > Regarding the release procedure, the document we have been using has > guided past releases, and overall, it is accurate. The complexity in > previous releases came mainly from the pipelines. For 10.0.0, it was > the first time running them end-to-end, so many issues surfaced during > the release itself. For 10.1.0, we went through another complex cycle > as important changes in kie-tools required a large number of fixes > before the pipelines could stabilize again. Hopefully, this cycle will > be less disruptive. > > For reference, the PR proposing improvements has been open for a while [1] > > And the release procedure document I mentioned, originally authored by > Tiago, is here [2]. > > I'm, of course, happy to help wherever needed. > > [1] - https://github.com/apache/incubator-kie-tools/pull/3293 > [2] - > https://docs.google.com/document/d/15V-1e62bmmWeOdFUnSJHymPYoeb0TTwp0bhxPuJn4zo/edit?tab=t.0 > > - > Alex > > On Mon, Dec 8, 2025 at 12:49 PM Kennedy Bowers <[email protected]> wrote: > > > > Hi all, > > > > Thanks Alex for volunteering to help with the 10.2 release, and apologies > > for my recent absence. I would be very grateful for your help, so we can > > get the release out on something close to the planned schedule. It would be > > great to have all required 10.2 changes merged into main and the > > documentation updated so that anyone in the community can confidently > > follow the process for future releases. > > > > I’d also like to continue serving as release manager for 10.2. I believe it > > will benefit the project if we start establishing a pattern of distributing > > release knowledge now, rather than allowing it to stay concentrated. While > > this might cause a slight delay for the current release, I believe in the > > long-run it will be beneficial for the community and get us a step closer > > to documenting the release process in such a way that someone with no > > experience will be able to manage a release in future. > > > > Before we branch for 10.2, we still have a few outstanding tasks: the > > remaining 10.1 sync PRs need to be merged, and the GWT-based editors need > > to be removed. Once those are wrapped up, we should be in a strong position > > to begin the release process. In the meantime, I’ll continue testing the > > pipelines to help ensure everything is ready as soon as the necessary code > > changes are in place. > > > > Looking forward to working together on this! > > > > Kind regards, > > Kennedy > > > > > > On 2025/11/19 13:01:21 Alex Porcelli wrote: > > > Hi Tiago, > > > > > > Thanks for the note. Rotation is healthy and important to prevent > > > knowledge from concentrating in just a few people. > > > > > > At the same time, we have to balance rotation with the ability > > > actually to deliver a release. We are now more than a month without > > > any communicated progress on 10.2, one Release Manager is leaving, and > > > we have not heard from Kennedy during this period. I fully understand > > > that he is on vacation and will be returning soon, but the combination > > > of circumstances puts the project in a difficult position. > > > > > > Since 10.1, we have accumulated several bug fixes, new functionality, > > > and most importantly, a significant number of vulnerabilities. Based > > > on experience, even if we reset today, it is unlikely that we would > > > see a release before January 2026. And that estimate assumes the > > > involvement of people who have already been through the release > > > process. > > > > > > I sincerely appreciate IBM stepping in to help with releases. But > > > given the internal shifts that Jason mentioned, this may not be the > > > best moment to rely on that transition as the foundation for the 10.2 > > > timeline. > > > > > > This is why Eduardo and I offered to step in. We have handled previous > > > releases and can provide continuity so the community does not lose > > > more time. And to be clear, we are 100 percent aligned on getting > > > Kennedy involved as soon as he is available and if he still wants to > > > participate. The offer is to keep the momentum, not to exclude anyone. > > > > > > The goal here is to ensure the project gets the release out sooner. > > > > > > - > > > Alex > > > > > > On Tue, Nov 18, 2025 at 10:55 PM Tiago Bento <[email protected]> > > > wrote: > > > > > > > > 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] > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [email protected] > > > For additional commands, e-mail: [email protected] > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
