[POLL] 8.1 Patch Or Not

classic Classic list List threaded Threaded
13 messages Options
Reply | Threaded
Open this post in threaded view
|

[POLL] 8.1 Patch Or Not

jtgreene
Administrator
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
[hidden email]
https://lists.jboss.org/mailman/listinfo/wildfly-dev
Reply | Threaded
Open this post in threaded view
|

Re: [POLL] 8.1 Patch Or Not

Dimitris Andreadis
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
> [hidden email]
> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>
_______________________________________________
wildfly-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/wildfly-dev
Reply | Threaded
Open this post in threaded view
|

Re: [POLL] 8.1 Patch Or Not

Arun Gupta
+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 <[hidden email]> 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
>> [hidden email]
>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>>
> _______________________________________________
> wildfly-dev mailing list
> [hidden email]
> https://lists.jboss.org/mailman/listinfo/wildfly-dev



--
http://blog.arungupta.me
http://twitter.com/arungupta

_______________________________________________
wildfly-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/wildfly-dev
Reply | Threaded
Open this post in threaded view
|

Re: [POLL] 8.1 Patch Or Not

James Perkins
In reply to this post by Dimitris Andreadis
+1

If both isn't a huge deal, I say both.

On 05/28/2014 02:48 PM, Dimitris Andreadis 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
>> [hidden email]
>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>>
> _______________________________________________
> wildfly-dev mailing list
> [hidden email]
> https://lists.jboss.org/mailman/listinfo/wildfly-dev

--
James R. Perkins
JBoss by Red Hat

_______________________________________________
wildfly-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/wildfly-dev
Reply | Threaded
Open this post in threaded view
|

Re: [POLL] 8.1 Patch Or Not

Vaclav Tunka
In reply to this post by Arun Gupta
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 <[hidden email]> 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
>>> [hidden email]
>>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>>>
>> _______________________________________________
>> wildfly-dev mailing list
>> [hidden email]
>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>
>
>

--
Vaclav Tunka
Enterprise Application Platforms
JBoss by Red Hat
_______________________________________________
wildfly-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/wildfly-dev
Reply | Threaded
Open this post in threaded view
|

Re: [POLL] 8.1 Patch Or Not

Tomaž Cerar-2
In reply to this post by jtgreene
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 <[hidden email]> 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
[hidden email]
https://lists.jboss.org/mailman/listinfo/wildfly-dev


_______________________________________________
wildfly-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/wildfly-dev
Reply | Threaded
Open this post in threaded view
|

Re: [POLL] 8.1 Patch Or Not

Darran Lofthouse
In reply to this post by James Perkins
+1 If we have the capability I think we should be providing the option
for it to be used.

An additional point, size is not the only motivation for a patch - using
a patch means the end users don't need to start with a clean install if
they have an existing installation.

Regards,
Darran Lofthouse.


On 29/05/14 01:12, James R. Perkins wrote:

> +1
>
> If both isn't a huge deal, I say both.
>
> On 05/28/2014 02:48 PM, Dimitris Andreadis 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
>>> [hidden email]
>>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>>>
>> _______________________________________________
>> wildfly-dev mailing list
>> [hidden email]
>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>
_______________________________________________
wildfly-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/wildfly-dev
Reply | Threaded
Open this post in threaded view
|

Re: [POLL] 8.1 Patch Or Not

kkhan

On 29 May 2014, at 11:09, Darran Lofthouse <[hidden email]> wrote:

> +1 If we have the capability I think we should be providing the option
> for it to be used.
>
> An additional point, size is not the only motivation for a patch - using
> a patch means the end users don't need to start with a clean install if
> they have an existing installation.
Yes, apart from just standalone.xml, carrying over JDBC drivers (and probably other things I forget) should be useful too

>
> Regards,
> Darran Lofthouse.
>
>
> On 29/05/14 01:12, James R. Perkins wrote:
>> +1
>>
>> If both isn't a huge deal, I say both.
>>
>> On 05/28/2014 02:48 PM, Dimitris Andreadis 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
>>>> [hidden email]
>>>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>>>>
>>> _______________________________________________
>>> wildfly-dev mailing list
>>> [hidden email]
>>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>>
> _______________________________________________
> wildfly-dev mailing list
> [hidden email]
> https://lists.jboss.org/mailman/listinfo/wildfly-dev


_______________________________________________
wildfly-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/wildfly-dev
Reply | Threaded
Open this post in threaded view
|

Re: [POLL] 8.1 Patch Or Not

Darran Lofthouse
On 29/05/14 11:24, Kabir Khan wrote:

>
> On 29 May 2014, at 11:09, Darran Lofthouse <[hidden email]> wrote:
>
>> +1 If we have the capability I think we should be providing the option
>> for it to be used.
>>
>> An additional point, size is not the only motivation for a patch - using
>> a patch means the end users don't need to start with a clean install if
>> they have an existing installation.
> Yes, apart from just standalone.xml, carrying over JDBC drivers (and probably other things I forget) should be useful too

Deployments, vault instances, key and trust stores, properties files
containing their users, integration as a service on their os, tweaked
memory settings ....

And I am sure I have missed another bunch of things an end user may have
added to a clean distro ;-)

>>
>> Regards,
>> Darran Lofthouse.
>>
>>
>> On 29/05/14 01:12, James R. Perkins wrote:
>>> +1
>>>
>>> If both isn't a huge deal, I say both.
>>>
>>> On 05/28/2014 02:48 PM, Dimitris Andreadis 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
>>>>> [hidden email]
>>>>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>>>>>
>>>> _______________________________________________
>>>> wildfly-dev mailing list
>>>> [hidden email]
>>>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>>>
>> _______________________________________________
>> wildfly-dev mailing list
>> [hidden email]
>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>
_______________________________________________
wildfly-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/wildfly-dev
Reply | Threaded
Open this post in threaded view
|

Re: [POLL] 8.1 Patch Or Not

Jason T. Greene
In reply to this post by Tomaž Cerar-2

On May 29, 2014, at 3:56 AM, Tomaž Cerar <[hidden email]> wrote:

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?


I like the optional fix up script idea a bit better because it would correct all of the old "disabled" jars. Although the 2 patch solution would have to be used in a future release for updating to the new format. We also should look into the possibility of dynamic bootstrapping of new patch behavior in the patch itself. This would allow us to introduce new formats without an intermediary patch. 



On Wed, May 28, 2014 at 11:23 PM, Jason Greene <[hidden email]> 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
[hidden email]
https://lists.jboss.org/mailman/listinfo/wildfly-dev


_______________________________________________
wildfly-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/wildfly-dev
Reply | Threaded
Open this post in threaded view
|

Re: [POLL] 8.1 Patch Or Not

Andrig Miller
In reply to this post by jtgreene
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" <[hidden email]>
> To: "WildFly Dev" <[hidden email]>
> 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
> [hidden email]
> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>

_______________________________________________
wildfly-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/wildfly-dev
Reply | Threaded
Open this post in threaded view
|

Re: [POLL] 8.1 Patch Or Not

jtgreene
Administrator
Ok so the universal feedback is that we release the mega-patch anyway.

On May 29, 2014, at 10:54 AM, Andrig Miller <[hidden email]> 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" <[hidden email]>
>> To: "WildFly Dev" <[hidden email]>
>> 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
>> [hidden email]
>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>>

--
Jason T. Greene
WildFly Lead / JBoss EAP Platform Architect
JBoss, a division of Red Hat


_______________________________________________
wildfly-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/wildfly-dev
Reply | Threaded
Open this post in threaded view
|

Re: [POLL] 8.1 Patch Or Not

jtgreene
Administrator
In reply to this post by Andrig Miller
Ok so the universal feedback is that we release the mega-patch anyway.

On May 29, 2014, at 10:54 AM, Andrig Miller <[hidden email]> 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" <[hidden email]>
>> To: "WildFly Dev" <[hidden email]>
>> 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
>> [hidden email]
>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>>

--
Jason T. Greene
WildFly Lead / JBoss EAP Platform Architect
JBoss, a division of Red Hat


_______________________________________________
wildfly-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/wildfly-dev