[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [mylar-dev] enhancements in Mylar team API
|
Michael Valenta wrote:
I don't really view these as three different cases. CVS and Subversion
are very similar capability wise in this respect (i.e. neither have
the concept of a change set built in). I can see the argument that the
classes be made API so they can be used by other repository providers
that do not have the concept. However, there are repositories out
there that do have the concept and would therefore already have their
own implementations. You motivation fore maming the classes API seems
to be so that 3d party tooling like Mylar can use it. As I have said
before, this is a mistake. Mylar should have API that defines what it
requries from change sets but leave the implementation up to the
repository provider.
Right, but that team provider could of as well used that API to
represent their change set model, or as you suggested to Mylar provide a
bridge to that API.
I a also agree with Mik that bridge is not too easy to implement
because structures are relatively deep. We will have to do that in Mylar
first, and then and then repository providers will have to do that again.
> Also, you said that team working on Platform/Team does not have man
> power for this. On the other hand there is at least 3 commercial
vendors
> are currently building team providers (p4, Subversive and
> Rational/Jazz). Would it be possible to request some man power for this
> task from those teams? In a result everybody will benefit from this.
I find that the repository vendors are usually pretty resource
strapped as well (it seems to be a common affliction). However, if you
feel strongly about this, then I would suggest that you contact these
and other repository vendors to see if they are willing to participate.
I sort of hoped that you may already have some contacts. :-)
regards,
Eugene
