 |
|
This page uses release 22.1.1 as a version example. We recommend always using the latest versions of code and data.
|
|
|
 |
Ensembl Versioning Scheme |
 |
|
|
|
|
|
The Ensembl versioning scheme is really three versioning schemes - one for each of the API, the data, and the webcode. The three schemes have the API version in common, because the data and the webcode work with each other through the API. The fundamental idea is that if the data, the webcode, and the API all have the same API version, then they will be compatible.
|
|
|
|
|
Ensembl API Versioning |
|
|
|
As everything has the API version in common, then it makes sense that the API version should be the simplest. It is just a number; 22 for the 22.1.1 release, 23 for the next change in the schema.
The API can be checked out of cvs with the tag "branch-ensembl-versionnumber", e.g branch-ensembl-22 for the 22.1.1 release.
|
|
|
|
Ensembl Data Versioning |
|
|
|
The data version number is made up of the API version that works with that database, and a version number for the data itself. A letter suffix to the data version indicates a change in data without a change in assembly; e.g. a new gene build. For the 22.1.1 release, the data version number is 22.1. The 1 in this comes from the fact that it is the first chicken assembly number.
The name of the chicken core database for the 22.1 release is therefore gallus_gallus_core_22_1.
|
|
|
Ensembl Web code Versioning |
|
|
|
The webcode version is very similar to the data version in that it consists of the API version and its own incremental version number. For the 22.1.1 release, the webcode version is 22.1. If another website is released before the API changes version, then it will be 22.2.
The webcode can, like the API, be checked out of cvs with the tag "branch-ensembl-versionnumber", e.g branch-ensembl-22-1 for the 22.1.1 release.
|
|
|
Gallus_gallus 