Earlier today Yeray tagged the WildFly Core release we plan to use for WildFly 37 Beta, thank you Yeray I will merge once CI completes.

I have taken a pass through the pull request queue, the following shows the PRs I am focussed on including before the WildFly 37 Beta release:

https://github.com/wildfly/wildfly/pulls?q=is%3Aopen+is%3Apr+label%3A37.x

For mergers please feel free to merge other PRs if they are ready and if there is anything else you would like me to pay attention to merging before the Beta release please get the 37.x label added and I have also been adding the Critical label for the subset we really want in before Beta.

I have added a follow up PR to Brian's GPG signing PR in case we want to include the detached signatures in our uploads to enable users to verify the signatures - it feels like if we are ready to start signing we should include the signatures now. I will need to follow up with some changes to the downloads page next week if we would like to include these.

For each download artifact we should add a link to the signature.
For the release we should add a link to the individual that performed the release so users can check against the correct contributor.

If someone could please merge my key information PR to wildfly.org that would also be great https://github.com/wildfly/wildfly.org/pull/795 - thank you.

Just let me know if there is anything else you think I need to be aware of for this release.

Regards,

Darran Lofthouse.

On Tue, Jun 17, 2025 at 7:58 PM Brian Stansberry <bstansbe@redhat.com> wrote:

Darran, another one to get into Beta is https://github.com/wildfly/wildfly/pull/19002

On Tue, Jun 17, 2025 at 9:35 AM Brian Stansberry <bstansbe@redhat.com> wrote:
I've fixed (unless CI disagrees) the metrics issued and rebased that PR. So it no longer shows the 5 commits that are already merged; just the ones specific to that PR.

On Tue, Jun 17, 2025 at 8:22 AM Brian Stansberry <bstansbe@redhat.com> wrote:

On Tue, Jun 17, 2025 at 8:21 AM Brian Stansberry <bstansbe@redhat.com> wrote:
The JBoss Threads 3.9.1 upgrade at https://github.com/wildfly/wildfly-core/pull/6440 would be good. If it's not in the Beta it should wait for WF 38.

Unfortunately there's some issue related to thread pool metrics where my fix attempt last night didn't work. I'll poke a bit more. But if others could review the PR that would be good.

BTW, I mean review it in general, not particularly related to the metrics thing. :)

Note: that PR has 9 commits, but the first 5 are from another PR https://github.com/wildfly/wildfly-core/pull/6438 that was merged earlier today. So don't bother looking at those.

On Mon, Jun 16, 2025 at 8:29 AM Darran Lofthouse <darran.lofthouse@jboss.com> wrote:
FYI this is just a quick reminder that changes targeting WildFly 37 Beta pull requests are due in this coming Wednesday.

If there is anything you are trying to get in for WildFly 37 Beta please feel free to reply to this message or ping me directly to let me know.

As usual we will continue to merge bug fixes after the Beta release and before Final but also let me know if you have any fixes you would like to try and get into Beta.

--
Darran Lofthouse
Red Hat
darran.lofthouse@jboss.com
_______________________________________________
wildfly-dev mailing list -- wildfly-dev@lists.jboss.org
To unsubscribe send an email to wildfly-dev-leave@lists.jboss.org
Privacy Statement: https://www.redhat.com/en/about/privacy-policy
List Archives: https://lists.jboss.org/archives/list/wildfly-dev@lists.jboss.org/message/BLQWZ3STKVSBSJCIO5MJXUJNFZCKEVKN/

--
Brian Stansberry
Principal Architect, Red Hat JBoss EAP
WildFly Project Lead
He/Him/His

--
Brian Stansberry
Principal Architect, Red Hat JBoss EAP
WildFly Project Lead
He/Him/His

--
Brian Stansberry
Principal Architect, Red Hat JBoss EAP
WildFly Project Lead
He/Him/His

--
Brian Stansberry
Principal Architect, Red Hat JBoss EAP
WildFly Project Lead
He/Him/His