Hi,
I'm not affiliated with JBoss or Red Hat, just a user and therefor not
able to give any "official answer", but as a mere user I'm not
bothered much by this. WildFly versions are just milestones on the
road to the next EAP version anyway.
So whether you have {EAP 6, m1, m2, m3, m4, EAP 7}, or {EAP 6, wf8,
wf9, wf10, EAP 7} doesn't make a lot of difference to me.
From another point of view, Chrome has been been updating major
versions for every small thing for a long time now, where before
browsers used to be on some major version like forever and incremented
minor. It doesn't mean Chrome is making larger leaps, it's just a
numbering for which no universal rules have really been set.
E.g. Vendor X's version 10.12.Alpha-1.a.3 may be comparable to
Vendor's Y version 0.53. Hard to compare.
Kind regards,
Arjan Tijms
On Wed, Aug 19, 2015 at 3:38 PM, Karl Pietrzak <kap4020(a)gmail.com> wrote:
Hi everyone!
First off, kudos to everyone for a great product!
Secondly, I'm wondering if someone could explain to me the significance of
the quick succession of Wildfly version upgrades: from 8 -> 9 -> 10 (soon).
It seemed like we were on JBoss 7.x for a long time, and now the top link at
http://wildfly.org/downloads/ is actually the Wildfly 10.x beta.
Does this represent:
1. a sudden increase in contributions and feature work?
2. shift in marketing (i.e., no underlying tech changes)
3. something else
Our concern is that this represents some instability / internal dynamics /
change in policy that would encourage us to visit other app servers.
Thank you!
--
Karl
_______________________________________________
wildfly-dev mailing list
wildfly-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/wildfly-dev