Hadley Wickham

Because the jobs were never run

Start building out some testing infrastructure

1

@gaborcsardi if you think this seems like a reasonable starting point, I'll keep fleshing it out a bit.

So we can (e.g.) use it to generate googlesheets

To maybe first and last 50 lines? ### CRAN ``` * installing *source* package ‘BMSC’ ... ** package ‘BMSC’ successfully unpacked and MD5 sums checked ** libs "/Library/Frameworks/R.framework/Resources/bin/Rscript" -e "source(file.path('..',...

(rather than the first). This makes interactive usage a bit easier.

Might just be a csv file that could easily be uploaded Here's what we're going for ggplot2: https://docs.google.com/spreadsheets/d/1UZIFwt3j3XjnRGOMNJZvpal_CAj7Hz8aNXJt41m3JjM/edit#gid=0

Compare two development versions

3

When considering an API breaking change, it is useful to be able to empirically determine the impact by comparing revdeps from a branch with revdeps on master.

Document possible value of status somewhere

3

Because I keep getting confused

Consider producing individual package reports

1

Instead of one giant `problems.md`. This would make life easier for large packages like testthat, and give more space to inline all test failures.