2012/6/5, David Anderson <[email protected]>: > Any branch called *core* > (which should actually be *client*; "core" is deprecated) > is a client release, and the non-client code (server, API) > is in an indeterminate state.
I think this could justify putting the client and the server in separate git repositories. Each repository would have its own tags and branches. The server.git/stable branch would have no client code, and client.git/7.0 would have no server code, thus no branch would have code in an "indeterminate state". It would also make both repos smaller, so that developers or users interested in one part don't have to download the whole history of the other. The problem is the shared code in lib/. Putting it in a third repository and configuring it as a git-submodule of the other two would work, but might be too cumbersome. I asked for help and suggestions on how to solve that issue, but unfortunately I only got useless suggestions, such as doing versioned releases of the server together with the client (which is completely impractical). -- Nicolás _______________________________________________ boinc_dev mailing list [email protected] http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address.
