On 01/07/2011 12:04 PM, Gerry Reno wrote:
Heinz, Ok, but is this really going to work?
The various components that make up 'all' of x2go should be in their
own project.
So for example, x2goclient should be a separate project from x2goserver. This way each of them can have their own release version numbers. If you have the entire x2go under one project then the entire
project, clients, servers, all of it will have a new version number (tag) each time you release any new part of the codebase. DVCS operates on versioning the entire codebase and not on versioning separate files as was the case with CVS.
So if you have a stable server, 3.0.1-XX, but you have new clients
coming along and changing, the only way to prevent the server release from also incrementing is to have the clients and server separated into separate projects. And that way each would have their own release numbering scheme.
Regards, Gerry
Check here for an explanation of possible layouts:
http://stackoverflow.com/questions/2732020/git-repository-layout-for-server-...
Regards, Gerry