The other solution will be to keep oak-segment and oak-tarmk-standby as deprecated modules in 1.6.x and remove them in 1.8.
2016-11-01 14:00 GMT+01:00 Francesco Mari <[email protected]>: > 2016-11-01 12:56 GMT+01:00 Julian Reschke <[email protected]>: >> On 2016-11-01 11:44, Francesco Mari wrote: >>> >>> Hi, >>> >>> 2016-11-01 11:38 GMT+01:00 Robert Munteanu <[email protected]>: >>>> >>>> Hi Francesco, >>>> >>>> On Tue, 2016-11-01 at 10:16 +0100, Francesco Mari wrote: >>>>> >>>>> Hi, >>>>> >>>>> This is a heads up for the deprecation oak-segment and >>>>> oak-tarmk-standby. The new oak-segment-tar module is a replacement >>>>> for >>>>> both of the aforementioned modules. If somebody is concerned about >>>>> the >>>>> deprecation, please let me know. >>>> >>>> >>>> A couple of 'outsider' questions: >>>> >>>> 1. What does the deprecation mean exactly? >>> >>> >>> It means that we are marking every class in those modules as >>> @Deprecated. These modules will have a 1.6 release, but will probably >>> be removed from the reactor after that to exclude them from further >>> releases. >>> ... >> >> >> That doesn't sound right to me. >> >> Either remove them *before* 1.6 is cut, or keep them in the 1.6 branch later >> on. > > I think that we will need at least a 1.6 release for oak-run and > oak-upgrade to correctly use the tooling for the migration. > >> Best regards, Julian
