Versioning mechanisms

BOINC is designed to accommodate evolution of both the infrastructure (the core client and scheduling server) and of applications.

Projects are free to release as many application versions as they like. All core client releases should be coordinated through the BOINC project at U.C. Berkeley.

Each core client version in the BOINC database has the following attributes:

• message: if the scheduling server gets a request from this version of the core client, it returns this message (e.g., suggesting that the user update the core client).
• deprecated: if true, this instructs the scheduling server to not send any work to hosts running this version.

Each application version has the following attributes:

• min core version: Don't run the application on core clients earlier than this.
• max core version: If nonzer, don't run the application on core clients later than this.