who's doing what? (was Re: [CAF] CAF development roadmap)

[G. Matthew Rice]

Michael Graham <magog at the-wire.com> writes:
> I think SVK and darcs both do this.  It's the "smart merge" (or "star
> merge") thing.  But that may be a different feature I'm thinking of.  My
> head goes all swimmy when I think about branch merging.

I'm uncertain if they're the same.  Sorry.  My experience is limited to SCCS,
RCS, CVS, ClearCase, PVCS, VSS, SVN (only a little, too) and Perforce.  Plus
some home-brewed garbage that some clients have cooked up.

If they suffer from the same 'checkout one branch per client' problem as RCS,
CVS, SVN, ... it will still be annoying for doing things where you want more
than one branch at a time (I'll let you come up with scenarios).


> Over the summer we were talking about integrated scm+rt+wiki solutions
> like  Trac.  The hope is that we can eventually do this with SVN/Darcs +
> RT + Kwiki.

np.  Like I said, I'm happy to have a branch to work on where I can submit.
If we want to make use of LPI's RT, we could add more queues.  Add a wiki,
more mailing list, whatever...

<wink>I've convinced, and the LPI board agree, that LPI should be viewed as
producers of FOSS and not just consumers.</wink>

We'll be releasing the apps that Richard started that are based on CAF but
I'm happy to provide any support for CAF itself, too.


> Hey that's pretty cool!  I guess that's the centralized repository approach
> to distributed version control.  In SVK or darcs, each developer would have
> his own personal repository on his own machine instead of a writable branch
> on the server.

Both models work.  It just depends on which person (project 'owner'
vs. developer) is the biggest control freak the determines which model is
best ;)

Regards,
-- 
g. matthew rice <matt at starnix.com>           starnix, toronto, ontario, ca
phone: 647.722.5301 x242                                  gpg id: EF9AAD20
http://www.starnix.com              professional linux services & products