On Mon, Dec 9, 2024 at 12:07 PM Brian Stansberry <
brian.stansberry(a)redhat.com> wrote:
Hi everyone,
We're planning to target WildFly 35 Final on Wednesday January 8.
s/target/tag
We tag on the 8th and bits are available on
wildfly.org on the 9th.
To hit this target we need all PRs for changes that will go into 35
Final
to be **ready for merge by next Wednesday December 18**.
So in a bit over a week.
By ready for merge we mean with code review approvals by the relevant
people and with acceptable CI results.
We need things done by then in order to have time to merge them and do a
WildFly Core release before people go off for PTO.
If something critical comes up over the year end vacation period we can
handle PRs to fix it that are ready for merge by Thursday January 2. **No
one should plan now on using that Jan 2 deadline; it's only for responding
to unexpected events.** Many people will not be back from holidays that
first week of January. There will be no capacity to deal with a bunch of
changes. Get things done by Dec 18 or count on it waiting until WildFly 36.
Best regards,
--
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