Dev to QA Handoff: Difference between revisions
No edit summary |
mNo edit summary |
||
| Line 1: | Line 1: | ||
After you have finished creating a track and it is ready for QA, you should add an entry to the qapushq table on hgwbeta. | After you have finished creating a track and it is ready for QA, you should add an entry to the qapushq table on hgwbeta. | ||
There is a | There is a [http://hgwbeta.cse.ucsc.edu/cgi-bin/qaPushQ CGI] for this. | ||
'''Add a track to the pushQ only if everything is ready.''' | '''Add a track to the pushQ only if everything is ready.''' | ||
This includes: | This includes: | ||
* All tables have been built | |||
* TrackDb has been edited (including track and search lines as appropriate) | |||
* Make alpha on hgwdev in /trackDb directory | |||
* All underlying files are complete and in the correct location (usually /gbdb/) | |||
* All associated downlads files have been created and are in the correct location (usually /data/apache/htdocs/goldenPath/) | |||
'''Editing the pushQ entry:''' | '''Editing the pushQ entry:''' | ||
''RELEASE LOG:'' | ''RELEASE LOG:'' | ||
Put the main identifier, usually short label followed by comments in parentheses if any (e.g. Known Gene (data update)). No need to enter the database name. | |||
''TABLES:'' | ''TABLES:'' | ||
Don't forget to include: | |||
* trackDb | |||
* hgFindSpec (if the items in this track are searchable) | |||
* extFile | |||
* seq | |||
''FILES:'' | ''FILES:'' | ||
Don't forget to include: | |||
* download files | |||
''CGIs:'' | ''CGIs:'' | ||
If this track depends on a particular upcoming release of the CGIs, enter the CGI name and the version number here (e.g. hgTracks (v140)). | |||
''EXTERNAL SOURCE:'' | ''EXTERNAL SOURCE:'' | ||
Enter the name and email address of the collaborator. Or enter the name of the website or lab where the data came from. | |||
''NOTES:'' | ''NOTES:'' | ||
Add notes to the QA team in this section. Be as specific as possible -- the more you enter here, the less QA will have to ask you for. Also, if this track has been requested by a user, enter the user's email address here. QA will send an email to that user after the track has been pushed to the RR. | |||
If this is the release of an entire assembly, use Angie's [[makePushQSql.pl]] script. | If this is the release of an entire assembly, use Angie's [[makePushQSql.pl]] script. | ||
[[Category:Browser QA]] | [[Category:Browser QA]] | ||
Revision as of 22:14, 15 August 2006
After you have finished creating a track and it is ready for QA, you should add an entry to the qapushq table on hgwbeta. There is a CGI for this.
Add a track to the pushQ only if everything is ready. This includes:
- All tables have been built
- TrackDb has been edited (including track and search lines as appropriate)
- Make alpha on hgwdev in /trackDb directory
- All underlying files are complete and in the correct location (usually /gbdb/)
- All associated downlads files have been created and are in the correct location (usually /data/apache/htdocs/goldenPath/)
Editing the pushQ entry:
RELEASE LOG: Put the main identifier, usually short label followed by comments in parentheses if any (e.g. Known Gene (data update)). No need to enter the database name.
TABLES: Don't forget to include:
- trackDb
- hgFindSpec (if the items in this track are searchable)
- extFile
- seq
FILES: Don't forget to include:
- download files
CGIs: If this track depends on a particular upcoming release of the CGIs, enter the CGI name and the version number here (e.g. hgTracks (v140)).
EXTERNAL SOURCE: Enter the name and email address of the collaborator. Or enter the name of the website or lab where the data came from.
NOTES: Add notes to the QA team in this section. Be as specific as possible -- the more you enter here, the less QA will have to ask you for. Also, if this track has been requested by a user, enter the user's email address here. QA will send an email to that user after the track has been pushed to the RR.
If this is the release of an entire assembly, use Angie's makePushQSql.pl script.
