Re: Subversion

> I agree too, I really like the idea of checking out files it helps reduce
> version conflict.

You don't check out(*) files in any way different than CVS.  What Subversion
does do differently is that it presents namespaces in a similar fashion to
a filesystem.  Our tree would look something like:

  /trunk    /bitpim
            /bpweb
  /releases /0.8.07
            /0.8.08
            /0.8.09

Say you wanted to develop some new feature, foo.  We'd have a new top
level structure /branches/simonc

You would do this:

  svn copy ..../trunk/bitpim ..../branches/simonc/foo

You would checkout /branches/simonc/foo and do whatever work you wanted
there.  Then use svn merge to bring the changes back to the trunk.

(*) By check out people sometimes mean that files are locked for editting.
CVS and SVN function in the same way - the difference is that SVN shows
the branches as a hierarchical name space whereas CVS uses named tokens
without altering the file hierarchy.

I think you meant what I described, and now it is explicitly laid out
for future reference.

BTW you could always have done this with CVS branches.

> I sometimes work with users in order to add support for new phones, this
> means sending them special test versions (I edit the test version in
> version.py), do you think that this new source control will allow me to
> baseline these test versions, I have lost code on occasion, so this would be
> useful.

I do want to automate grabbing version number and other unique conditions
out of the working tree information.  Some of it can be obtained by 
the keyword expansions and the rest can be grabbed at build time.
TortoiseSVN has a similar utility they use:
http://tortoisesvn.sourceforge.net/docs/release/TortoiseSVN_en/ch06.html

> Is there a way for me to use sourceforge to host test versions of bitpim?

The SourceForge release system is extremely manual, annoying and tedious
not to mention error prone.  You are welcome to subject yourself to it :-)
I have been looking for a command line tool that will automate all this
that uses Python.  That way I can trivially update from each build machine.
(I'd like to build on more Linux distros but won't until this file release
pain goes away.)  

The closest I have found is releaseforge.sf.net but for some unfathomable
reason the author chose to make it a gui tool.  SourceForge already gives
you crappy web pages - just changing them to a different gui is kinda 
silly.

Roger


-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642