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

Vaclav Tunka vtunka at redhat.com
Thu May 29 04:41:36 EDT 2014


I agree with Dimitris as well.

I am really looking forward for those per-class deltas. We should make 
sure we will ignore differences between various JDKs and associated 
compilers over various platforms. If I can help somehow, I will gladly 
do it.

Cheers,
Vaclav

On 05/29/2014 12:13 AM, Arun Gupta wrote:
> +1 to Dimitris's suggestion. This would particularly allow us to
> test/explain the mechanism that will be used in future WildFly builds.
>
> Any plans for individual technology to do WildFly patch-compatible releases ?
>
> Arun
>
> On Wed, May 28, 2014 at 2:48 PM, Dimitris Andreadis <dandread at redhat.com> wrote:
>> IMO, if the patch is almost as big as the full distro itself, that kind of defeats the
>> purpose. But you could provide both distros anyway and see from the download counts what
>> people are actually interested in, and maybe get some feedback on the patch mechanism, itself.
>>
>> /Dimitris
>>
>> On 28/05/2014 23:23, Jason Greene 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
>>>
>> _______________________________________________
>> wildfly-dev mailing list
>> wildfly-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>
>
>

-- 
Vaclav Tunka
Enterprise Application Platforms
JBoss by Red Hat


More information about the wildfly-dev mailing list