backend data base

[Vlad Skvortsov]

Joerg F. Wittenberger wrote:

[skipped]

>> Well, I would really be happy to see DITrack working with different 
>> backends. However, it's more of a resource management issue, rather
>> than 
>> a technical or ideological one. We just don't have enough resources to 
>> design the feature, write the glue code, test, debug, support and 
>> maintain it.
>>
>> Having a reasonably stable system working with a single backend is
>> what we are doing now. Especially taking into account that
>> Subversion is becoming a mainstream, at least in the open source
>> world.
>>     
>
> Fairly enough and about the route I'd suggest.
>
> What we could do, if we where to jump ship:
>
> 1.) We (here) would start using ditrack for askemos kernel
>   development, that's basically 2-3 users.  Via svn.  We'd gain
>   experience.
>   

Any update on that, Joerg?

> 2.) You document the backend assumtions and we both locate the best
>   API to plug into in the ditrack code.
>   

I've opened i#160 for this.

> 3.) We add a second backend.
>   

I think the easiest route to pursue here is to implement a "null" 
backend, i.e. no backend VCS at all. We'll just store data in a local 
filesystem. The next step might be CVS.

>> Well, if you feel you have enough driving force, we can start
>> thinking about abstracting out the working copy access API. The
>> first thing to do is, I believe, having a list of requirements for
>> the backend.
>>     
>
> See above, I should have read it all before starting to answer. ;-)
>
> Yes, that list would be, what we need first.
>   

:-) I'll work on that ASAP as my time permits.

-- 
Vlad Skvortsov, vss at 73rus.com, http://vss.73rus.com