Pre-pushq checklist: Difference between revisions
From Genecats
Jump to navigationJump to search
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
* look at a whole chromosome e.g. chr1, to check for pile ups. | |||
* maybe run by outside data contributor | |||
* makeDoc committed? | * makeDoc committed? | ||
* track html description committed? | * track html description committed? | ||
* if new tables: have you added them to makeDb/schema/all.joiner file. | |||
* if the track requires new CGI code: | * if the track requires new CGI code: | ||
** set the CGI target version of the redmine ticket, so QA will check the track against the new code when it goes out | ** set the CGI target version of the redmine ticket, so QA will check the track against the new code when it goes out | ||
* If this is a track that has been on the RR before: | * 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, e.g. any bed/bigBed fieldCount will break it. TrackDb is pushed constantly, you trackDb changes can go live at any time. | ** Does it have a release tag? If not: the new trackDb settings have to work with the old track, e.g. any bed/bigBed fieldCount will break it. TrackDb is pushed constantly, you trackDb changes can go live at any time. | ||
** If the track mysql columns change, then the track name must be different (add a version number, e.g. omim2) | ** If the track mysql columns change, then the track name must be different (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. | ** Is it used by more than one assembly, check the other assemblies. Unusual grp or parent settings may disable the track on other assemblies. | ||
Revision as of 10:35, 9 December 2014
- look at a whole chromosome e.g. chr1, to check for pile ups.
- maybe run by outside data contributor
- makeDoc committed?
- track html description committed?
- if new tables: have you added them to makeDb/schema/all.joiner file.
- if the track requires new CGI code:
- set the CGI target version of the redmine ticket, so QA will check the track against the new code when it goes out
- 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, e.g. any bed/bigBed fieldCount will break it. TrackDb is pushed constantly, you trackDb changes can go live at any time.
- If the track mysql columns change, then the track name must be different (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.
