Hi Eduardo,
This sounds completely reasonable!
Cheers,
Brian
On Thu, Mar 7, 2024 at 11:30 AM Eduardo Martins <emartins(a)redhat.com> wrote:
Hi there, so I just announced a new release of our migration tool,
and
would like to discuss a few changes wrt future releases.
The main issue is really the amount of effort needed to keep supporting as
many old WildFly versions as possible, so the proposed changes are:
* release a new version of the tool shortly after each major WildFly
release (e.g. 31.0.0.Final), which version should match WildFly's version
* limit the tool support to migrate TO ONLY that latest major WildFly
release
* limit the tool support to migrate FROM PREVIOUS 10 major WildFly releases
With those changes I believe we should be able to keep up with the time
boxed WildFly release frequency, except perhaps when we have very
significant changes, like the legacy security frameworks removal.
WDYT?
—E
_______________________________________________
wildfly-dev mailing list -- wildfly-dev(a)lists.jboss.org
To unsubscribe send an email to wildfly-dev-leave(a)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...
--
Brian Stansberry
Principal Architect, Red Hat JBoss EAP
WildFly Project Lead
He/Him/His