juneau-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gary Gregory <garydgreg...@gmail.com>
Subject Re: Breaking changes in 7.2.0. Plans for 7.2.1, 8.0.0
Date Thu, 11 Oct 2018 17:21:42 GMT
On Thu, Oct 11, 2018 at 11:17 AM James Bognar <jamesbognar@apache.org>
wrote:

> Yea I can do that.
>

Hi James,

My goal, which I hope you share is:

- Update from 7.1.0 to 7.2.1 as a drop-in replacement (skipping 7.2.0
altogether.)
- Follow the @deprecated warnings and update my source code.
- Update to the next release, whenever that is, as a drop in replacement.
Would that then be 8.0?

Is that how you see it?

Gary

>
> On Thu, Oct 11, 2018 at 1:15 PM Gary Gregory <garydgregory@gmail.com>
> wrote:
>
>> On Thu, Oct 11, 2018 at 10:47 AM James Bognar <jamesbognar@apache.org>
>> wrote:
>>
>>> Hi all,
>>>
>>> In hindsight, Juneau 7.2.0 should have been released as Juneau 8 due to
>>> breaking changes.  Particularly, the server and client side annotations
>>> were merged into a single set of annotations.  I'm now getting negative
>>> feedback for that decision (rightly so).
>>>
>>> My plan to fix this is to revert the changes made in 7.2.0 and to
>>> re-release 7.1.1 as 7.2.1.  Then release Juneau 8 with the latest bug fixes
>>> included.  Given the significant changes made in 7.2.0, I do not believe
>>> it's possible to fix backwards compatibility (just unmerging those
>>> annotations would explode the code complexity).
>>>
>>
>> Thank you for that. But will there be @deprecated comments so that we can
>> move to the new code?
>>
>> Gary
>>
>

Mime
View raw message