Pre-pushq checklist: Difference between revisions
From Genecats
Jump to navigationJump to search
No edit summary |
No edit summary |
||
| (4 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
* makeDoc | * look at a whole chromosome e.g. chr1, to check for pile ups. | ||
* makeDoc done? | |||
* track html description done? | |||
* if new mysql tables: added to makeDb/schema/all.joiner ? | |||
* maybe pass by outside data contributor | |||
* hdownload directory ? How does this work? Ask Jorge? | |||
* 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. | ** 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. | ||
** If the track mysql columns | *** Remember that trackDb is pushed constantly, your trackDb changes can go live at any time. | ||
** Is it used by more than one assembly, check the other assemblies. | ** If you changed the track's mysql columns, then the track name must be different (add a version number, e.g. omim2). We do not change mysql schemas. | ||
** Is it used by more than one assembly, check the other assemblies. An invalid grp or parent setting in the other assembly may disable the track. | |||
Latest revision as of 10:38, 9 December 2014
- look at a whole chromosome e.g. chr1, to check for pile ups.
- makeDoc done?
- track html description done?
- if new mysql tables: added to makeDb/schema/all.joiner ?
- maybe pass by outside data contributor
- hdownload directory ? How does this work? Ask Jorge?
- 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.
- Remember that trackDb is pushed constantly, your trackDb changes can go live at any time.
- If you changed the track's mysql columns, then the track name must be different (add a version number, e.g. omim2). We do not change mysql schemas.
- Is it used by more than one assembly, check the other assemblies. An invalid grp or parent setting in the other assembly may disable the track.
- 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.
