 |
|
This page uses release 31.2f as a version example. We recommend always using the latest versions of code and data.
|
|
|
 |
Ensembl Versioning Scheme |
 |
|
|
|
|
|
Each Ensembl release has an integer version number associated with it which is used to identify the correct versions of API, web code and databases that make up that release. The idea is that components with the same release version should work together - i.e. any web site built with 'version 31' API and web code, and 'version 31' databases should work correctly.
The BioMart code has its own versioning scheme, since it is independent of the Ensembl code - see the BioMart website for information on using the code separately, e.g. with the MartJ Java interface.
|
|
|
|
|
Ensembl Code Versioning |
|
|
|
For the API and web code, a CVS branch (essentially a named snapshot of the code) is made for each release and named with the release version number. The API and web code can be checked out of cvs with the tag "branch-ensembl-versionnumber", e.g branch-ensembl-31 for the 31.2f release.
|
|
|
|
Ensembl Data Versioning |
|
|
|
The Ensembl database names consist of the species, the database type, the release number, and the data version. A letter suffix to the data version indicates a change in data without a change in assembly; e.g. a new gene build.
The name of the Anopheles core database for the 31.2f release is therefore anopheles_gambiae_core_31_2f.
|
|
|
|
BioMart Versioning |
|
|
|
BioMart will branch less frequently than Ensembl, and the release number bears no relation to that of Ensembl. The first public release is version 0.2.
The code can be checked out of cvs - see the current version page or installation instructions for the cvs tag format.
|
|
|
Anopheles_gambiae 