Ok so the universal feedback is that we release the mega-patch anyway.
On May 29, 2014, at 10:54 AM, Andrig Miller <anmiller(a)redhat.com> wrote:
It would be nice, regardless of size of the patch, to get it out
there, and let people try it out. The more usage we get for the patch mechanism, the
better.
Andy
----- Original Message -----
> From: "Jason Greene" <jason.greene(a)redhat.com>
> To: "WildFly Dev" <wildfly-dev(a)lists.jboss.org>
> Sent: Wednesday, May 28, 2014 3:23:45 PM
> Subject: [wildfly-dev] [POLL] 8.1 Patch Or Not
>
> So we noticed two problems with releasing the patch for 8.1.0.Final
>
> 1. JBoss Tools Issues - Due to the patching mechanism in 8.0.0.Final
> “disabling" jars, applying the 8.1 patch will lead to warnings, this
> is fixed in their upcoming beta2 test. We have also removed the jar
> “disabling”, so future patches do not have this problem.
> 2. It’s Big - Due to the breadth of change in this release, the size
> of the patch is only slightly smaller than the distro. We have a
> planned improvement to support finer grained, per-class deltas,
> which would greatly reduce the size, but its not worth holding the
> release over (IMO).
>
> So the big question is assuming the above do you want a patch file
> for 8.1, or just a full distro only this time, and we instead ship a
> patch in a future 8.x release (we are considering doing an 8.2 with
> the CDI update that was pulled out of 8.1 due to TCK rules)?
>
> If there is enough demand considering 1 & 2 I would be happy to
> release one.
>
> Thanks!
> --
> Jason T. Greene
> WildFly Lead / JBoss EAP Platform Architect
> JBoss, a division of Red Hat
>
>
> _______________________________________________
> wildfly-dev mailing list
> wildfly-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/wildfly-dev
>
--
Jason T. Greene
WildFly Lead / JBoss EAP Platform Architect
JBoss, a division of Red Hat