In general everything is proceeding well with our preparations for the WildFly 32 Beta release, however with the introduction of the WildFly feature development process we have some work which is being completed.

It feels a shame that work which is almost ready will miss this Beta release by strictly applying the time box and we would really like to get the work we are doing into the hands of our community so we have decided we will push the release back by one week so some remaining items can be completed.

WildFly Core is already tagged and we are not planning a further WildFly Core tag unless a blocking issue is identified, we would now be aiming to tag WildFly 32 Beta on Wednesday the 3rd April so the release can be published on Thursday the 4th April.

--

Darran Lofthouse

Red Hat

darran.lofthouse@jboss.com