rscharpf/MinimumDistance — Issue #20: Tagging a CNV draft for a project
Author: rscharpf
Created: 2012-02-09 14:41:12+00:00
State: open

- CNV drafts should be created from Sweave files.

- The Sweave() file for producing a 'cnv draft' of a project will provide the session information used to create a particular draft by inclusion of the following codechunk:

<>=
toLatex(sessionInfo())
@

Note the version numbers packages that we maintain are not bumped for individual commits (nor should they be). A few things might be helpful here (until MinimumDistance / project package are more stable):

(1) cnv drafts should only be made from the collab branch of MinimumDistance (never a feature branch). There should be no uncommitted changes.

(2) All feature branches that are merged with the collab branch should bump the version number. Individual commits within a feature branch should not bump the version number.

(3) A tag of the MinimumDistance and project package might be helpful

(4) Project package: contains project-specific functions (e.g, whatever was required to create the Pedigree object / TrioSet object). The package should be versioned by git and tagged for each CNV draft.

(5) A naming convention for the tags. (?) maybe cnvDraft1_date...

As long as feature branches always bump the package version number prior to merging with collab, the session info should be sufficient for reproducibility. The tags will make rolling back easier.