QUOTE(dz @ Nov 4 2004, 10:28 AM)
Say you wrote a program called "Zaurus Robot Manager". The project name would be "Zaurus Robot Manager", while the unixname would be something like "zaurus_robot_manager". It's the name of the file under *nix; without any symbols and such.
But what is it good for my project? You can put any symbol (besides / and 0x00) into a Unix name - even a blank character.
Typically, I just have a project directory on my development machine with an arbitrary name ("mylargeproject"), a project name in the documentation ("Zaurus Robot Manager") and the name of the installer file (which could be "file3.ipk.gz" - who cares when clicking on the Download link?). I would just like to question if my local project name needs to be made transparent on ZSI.
Branches are just an extension to versions. For example, in Zaurus Robot Manager we have a stable version that we've released that runs great. We just made a new version, but it's not as stable. We still want people to test it out, so we create a new branch called "Unstable" and release it in there. When a new user goes to download your program and they're not a developer, they'll go for the Stable branch as opposed to Unstable.
I've used it when developing on Sourceforge and it works out pretty good
That sounds great and I might get used to as well. So it is more or less having several separate project release streams (feeds)... Or a single one but allowing to tag individual releases and allowing the user to filter by these tags.