Issues involving potential "server stable" releases:
1) What's included in the server release? My recommendation: everything except the client, i.e. web code, API, server code, scripts, wrappers. The complete package of what a new project would need. 2) Should the client and server release cycles be independent? I think so. Although there are exceptions, changes generally involve only one or the other. The points at which we want to branch and start testing will generally be different. 3) Assuming the cycles are independent, how should we number server releases? We could use the same numbering for both, but this has problems: - A sequence of releases in one part would cause gaps in the release numbers of the other part. - It would create the false impression that there's a connection or dependency between client and server releases with the same number. So my recommendation is that we start with 1.1.1 for the server version number. Thoughts/comments? -- David _______________________________________________ boinc_dev mailing list boinc_dev@ssl.berkeley.edu https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address.
