I'll not be tagging 33 Final today, as we're waiting for completion of some final testing. However, at this point I don't expect further changes in the wildfly/wildfly repo for 33.

Tagging tomorrow isn't great, as that means the main release announcement, availability of content on wildfly.org, etc happens on a Friday afternoon US time, with any post release deliverables not ready by then waiting until the next week. So my plan now is:

Mon Jul 22 -- Tag/deploy 33 Final
Tue Jul 23 -- Release available on wildfly.org
Wed Jul 24 -- Post release deliverables

Because I don't expect further changes in the wildfly/wildfly repo for 33, I've gone ahead and created the 33.x branch and opened up main for work on WildFly 34. Anyone needing to make any further changes to wildfly/wildfly for 33 will need to send PRs to both main and 33.x.

Best regards,

Brian

On Thu, May 16, 2024 at 5:46 PM Brian Stansberry <brian.stansberry@redhat.com> wrote:
We're aiming to have WildFly 33.0.0.Final available on wildfly.org on Thursday, July 18. The beta should be available on July 4.

Following are the key dates:

Wed Jun 26 -- Feature Freeze
Mon Jul 1 -- WF Core Beta release
Wed Jul 3 -- Tag/deploy 33 Beta
Thu Jul 4 -- Announce release

Wed Jul 10 -- Final PRs due
Mon Jul 15 -- WF Core Final release
Wed Jul 17 -- Tag/deploy 33 Final
Thu Jul 18 -- Release available on wildfly.org
Fri Jul 19 -- Post release deliverables

Best regards,

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