[wildfly-dev] [POLL] 8.1 Patch Or Not

[Tomaž Cerar]

Lets do both.

For many users I think having nice upgrade tool will help them move to
newer version. Even if upgrading is mostly just copying standalone.xml
over...

Btw, what if we would provide two part patch? first one that would fix the
jar invalidation and then proper one for 8.1 upgrade?


On Wed, May 28, 2014 at 11:23 PM, Jason Greene <jason.greene at redhat.com>
wrote:

> 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 at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/wildfly-dev/attachments/20140529/96249bbb/attachment.html