Re: Getting rid of deprecated OAK code

[Angela Schreiber <an...@adobe.com>]

hi

there is still quite some code left that is has "old"
in it's package name and/or is deprecated

is this code really still in use? why? if not, what is
the reason for not removing it? as stated below, i
don't see any compelling reason why we should ship
a new repo implementation with code that is already
outdated.

kind regards
angela

On 1/24/13 2:42 PM, Angela Schreiber wrote:
> hi devs
>
> i recently came across quite some new oak code that has
> already been marked deprecated... for example the old
> index implementations.
>
> would it be possible to get rid of those deprecated classes
> and methods? since OAK is a completely new repository
> implementation i don't see why we should have deprecated
> stuff in the very first official release...
>
> what do you think?
> angela

Re: Getting rid of deprecated OAK code

[Angela Schreiber <an...@adobe.com>]

i create a task at https://issues.apache.org/jira/browse/OAK-752
in order to remind us of this.

regards
angela

On 4/5/13 10:28 AM, Michael Dürig wrote:
>
> AFAIR the code mainly left there as a baseline while we switched to the
> new index implementation "p2". If it is still necessary for that I'm ok
> with keeping it longer. But we should definitely remove it from oak-core
> before we go 1.0. Maybe we should open an issue with the an 1.0 target
> so we don't forget.
>
> Michael
>
> On 4.4.13 18:25, Angela Schreiber wrote:
>> hi
>>
>> there is still quite some code left that is has "old"
>> in it's package name and/or is deprecated
>>
>> is this code really still in use? why? if not, what is
>> the reason for not removing it? as stated below, i
>> don't see any compelling reason why we should ship
>> a new repo implementation with code that is already
>> outdated.
>>
>> kind regards
>> angela
>>
>> On 1/24/13 2:42 PM, Angela Schreiber wrote:
>>> hi devs
>>>
>>> i recently came across quite some new oak code that has
>>> already been marked deprecated... for example the old
>>> index implementations.
>>>
>>> would it be possible to get rid of those deprecated classes
>>> and methods? since OAK is a completely new repository
>>> implementation i don't see why we should have deprecated
>>> stuff in the very first official release...
>>>
>>> what do you think?
>>> angela

Re: Getting rid of deprecated OAK code

[Michael Dürig <md...@apache.org>]

AFAIR the code mainly left there as a baseline while we switched to the 
new index implementation "p2". If it is still necessary for that I'm ok 
with keeping it longer. But we should definitely remove it from oak-core 
before we go 1.0. Maybe we should open an issue with the an 1.0 target 
so we don't forget.

Michael

On 4.4.13 18:25, Angela Schreiber wrote:
> hi
>
> there is still quite some code left that is has "old"
> in it's package name and/or is deprecated
>
> is this code really still in use? why? if not, what is
> the reason for not removing it? as stated below, i
> don't see any compelling reason why we should ship
> a new repo implementation with code that is already
> outdated.
>
> kind regards
> angela
>
> On 1/24/13 2:42 PM, Angela Schreiber wrote:
>> hi devs
>>
>> i recently came across quite some new oak code that has
>> already been marked deprecated... for example the old
>> index implementations.
>>
>> would it be possible to get rid of those deprecated classes
>> and methods? since OAK is a completely new repository
>> implementation i don't see why we should have deprecated
>> stuff in the very first official release...
>>
>> what do you think?
>> angela