Difference between revisions of "CSHL documentation"

From WormBaseWiki
Jump to navigationJump to search
Line 3: Line 3:
  
 
* [[Formal_development_strategy|Formal development strategy]] - ''An overview of the development process at WormBase''
 
* [[Formal_development_strategy|Formal development strategy]] - ''An overview of the development process at WormBase''
* [[Developer_notes Developer|notes]] - ''Best practices, conventions, etc''
+
* [[Developer_notes|Developer notes]] - ''Best practices, conventions, etc''
 
* [[Using_private_development_sites|Using private development sites]] - ''How to use the private, self-contained developer sites on brie3''
 
* [[Using_private_development_sites|Using private development sites]] - ''How to use the private, self-contained developer sites on brie3''
 
* [[Javascript_libraries Javascript|libraries]] - ''Javascript libraries in use at WormBase''
 
* [[Javascript_libraries Javascript|libraries]] - ''Javascript libraries in use at WormBase''

Revision as of 15:55, 24 September 2007

The WormBase Cold Spring Harbor team is in charge of developing, maintaining, and hosting WormBase. This page contains links to documentation relating to those topics.

Development

Administration

Hardware

General Admin

Virtual Machines / Freezes

Reimplementation

Hardware platform

Software platform

Administration

Load balancing and Failover

Logging

Monitoring

Reporting

Development notes by release

As part of the formal development strategy at WormBase, software freezes occur on the Wednesday before the release of each new database. This corresponds with the CSHL WormBase conference call.

For a new feature to enter production, developers must send an email to cshl@wormbase.org by the software freeze deadline briefly describing the new feature and any new module or database requirements. This section collates those notes for easy access