Forum OpenACS Improvement Proposals (TIPs): Re: TIP #25 (Proposed): No direct manipulation of the CVS repository

6: Re: TIP #25 (Proposed): No direct manipulation of the CVS repository (response to 5)

Posted by Malte Sussdorff on 10/18/03 09:44 AM

Okay, now please go ahead and kill me, but why are we sticking with CVS? Wouldn't it make sense in the recent light of events to have a look e.g. at subversion (I'd have said perforce, but they seemed to have changed their licensing policy). Just food for thought and I'm absolutely aware of the fact that subversion is still not in the 1.0 release state.

7: Re: TIP #25 (Proposed): No direct manipulation of the CVS repository (response to 6)

Posted by russ m on 10/18/03 10:28 AM

I had this exact conversation with Mark Aufflick yesterday - I don't think the "pre-beta" status of svn is really an issue for stability and repository safety (svn FAQ, some deployed sites). The problem is that they don't issue binaries and they're not guaranteeing client/server interoperability over more than a (3-week or so) release cycle, so everyone who currently works on OACS through CVS rather than release tarballs would need to start building svn client software and keeping it in sync with what is being run on the OACS repository. It's doable, and probably not that much of a problem for the companies and individuals who are the core of OACS development, but it places a burden on newcomers and casual developers that could well drive them off.

which sucks, because CVS blows goats and subversion fixes the bits that suck while keeping the familiar CVS UI...

If there's any interest in following this sort of path I'll find out what the actual (rather than "supported") level of compatibility is between cross-version clients and servers...

8: Re: TIP #25 (Proposed): No direct manipulation of the CVS repository (response to 7)

Posted by Joel Aufrecht on 10/18/03 03:12 PM

I think we should wait until it hits 1.0. Don't we already have enough prerequisite programs that haven't hit 1.0 yet?

10: Re: TIP #25 (Proposed): No direct manipulation of the CVS repository (response to 6)

Posted by Roberto Mello on 10/18/03 08:06 PM

Malte,

I've brought up this issue with the other OCT members. I am preparing documents, migration path, and a TIP for OpenACS to switch to using the GNU Arch SCM to replace CVS.

It is simple, has very advanced features for distributed repositories and merging, makes is much easier to maintain an OpenACS repository with your changes while still being able to synch with the main repository, etc.

Talli and Ben Bytheway are the ones who introduced me to it. I've been using it and it is great.

-Roberto

11: Re: TIP #25 (Proposed): No direct manipulation of the CVS repository (response to 10)

Posted by Benjamin Bytheway on 10/18/03 08:15 PM

In addition, GNU Arch HAS hit the 1.0 milestone. Version 1.1, which boasts a host of new features, is due out at the beginning of November.