Pre-pushq checklist
From Genecats
Jump to navigationJump to search
- check that makeDoc and track descriptions are committed
- if the track requires new code:
- set the CGI target version of the redmine ticket, so QA will check the track against the new code when it goes out
- look at a whole chromosome e.g. chr1, to check for pile ups.
- If this is a track that has been on the RR before:
- Does it have a release tag? If not: the new trackDb settings have to work with the old track (any bigBed fieldCount or schema changes will break it)
- If the table schema behind the track change, then change the track name (add a version number, e.g. omim2)
- Is it used by more than one assembly, check the other assemblies. Unusual grp or parent settings may disable the track on other assemblies.
