We're still sorting out some things to ensure we have a high quality
WildFly 27, so we won't be starting the release tomorrow or releasing this
week. How long it will take to finish up is still TBD. If you want to
follow discussions related to that, there's a Zulip thread at
https://wildfly.zulipchat.com/#narrow/stream/174184-wildfly-developers/to...
Best regards,
Brian
On Thu, Sep 22, 2022 at 5:57 PM Brian Stansberry <
brian.stansberry(a)redhat.com> wrote:
So, you might have noticed these dates were unrealistic! I think we
have a
better sense of when we'll finish up WF 27 now. Here's what we're planning:
27.0.0.Beta1:
WF Core PRs due -- Friday Sep 23
WF PRs due -- Monday Sep 26
Tag and release -- Wednesday Sep 28 / Thur Sep 29
27.0.0.Final:
WF Core code freeze -- Friday Oct 7
WF code freeze -- Monday Oct 10
Tag and release -- Wednesday Oct 12 / Thur Oct 13
Also, at this point a Dec 15 date for WildFly 28 Beta1 looks good, with 28
Final in the first half of January.
Best regards,
--
Brian Stansberry
Project Lead, WildFly
He/Him/His
On Tue, Aug 23, 2022 at 1:58 PM Brian Stansberry <
brian.stansberry(a)redhat.com> wrote:
> As we wrap up our work on WildFly 26.1.2 and on our EE 10 compliance for
> WildFly 27, I've been having some discussions re target dates for WildFly
> 27 Beta1 and Final.
>
> The following is what we're looking at:
>
> 27.0.0.Beta1:
>
> WF Core feature freeze -- Friday Sep 9
> WF feature freeze -- Monday Sep 12
> Tag and release -- Wednesday Sep 14 / Thur Sep 15
>
> 27.0.0.Final:
>
> WF Core feature freeze -- Friday Sep 23
> WF feature freeze -- Monday Sep 26
> Tag and release -- Wednesday Sep 28 / Thur Sep 29
>
> Beta1 will be like all WF betas in recent years -- feature complete and
> using .Final production code dependencies except for WF Core and _perhaps_
> one or two other components where we know we can produce and integrate a
> .Final within a day.
>
> Note that I expect we'll do a 27.0.0.Alpha5 at some point between now and
> Beta1. That will be like the other alphas for 27; just a deploy to JBoss
> Nexus and addition of the zip/tars to the downloads page. We'll do this to
> support our EE 10 compatibility certifaction requests.
>
> Best regards,
>
> --
> Brian Stansberry
> Project Lead, WildFly
> He/Him/His
>