Re: crm versions in CVS

   From: Jason Lewis <[email protected]>

   Hi Guys,

   It seems to me that the version control of crm is a little bit complex, 
   I'm not a source control expert but shouldn't all the versions of crm114 
   be in CVS and tagged appropriately so one could just get the tag required?

   And shouldn't each user's repository be a branch from trunk? I'm not 
   sure CVS can manage branches properly, but afaik, SVN can do branching 
   quite well.

   And also, maybe the crm code should be separate from the mailfilter and 
   mailreaver code? This would make managing installations easier for 
   admins I think.

   Just my two cents worth.

Yes, and no.

Though you are *probably* right that some kind of source code control
would be a darn good idea, the problem is that I've had some exceedingly
bad experiences with CVS / Subversion and found that Sourceforge's
systems to be less than useless.

So, the current state is that it's snapshots, and snapshots alone.
That's why I only put up tested versions plus the WGET bleeding edge.

And, philosopically speaking, I'm morally opposed to having a single
point of failure such as Sourceforge's server (which by the way they
do NOT warrant in any way).

On the other hand, GIT seems to overcome many of my objections; among
other things, every GIT repository is a fully functional master.

Ger: do you have a machine and an IP address that we can use as a 
host for GIT?

If not, I can punch a hole in my hardware firewall and put up a
machine that will be 24x7, albeit on a 128Kbyte DSL line.

    - Bill Yerazunis



-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/