tuning the hadleyverse repo

[cboettig]

@hadley Currently hadleyverse uses the current CRAN versions for all packages, including CRAN versions of all packages on the SUGGESTS lists (as opposed to whatever is available as debian binaries, etc), with the exception of reshape2, because not having hadley/reshape#46 fixed kills me). Curious if you think it might be handy to use the github versions of other packages, either by default or maybe as a hadleyverse:dev tag, or if you think most users are best off with the CRAN versions (since they can always explicitly upgrade later). Thanks for your input!

[eddelbuettel]

I have the feeling this question is 'too dynamic' ie the canonical answer will change with the commits, new packages, ... as time marches.

"Currently released on CRAN" is on the other hand a pretty decent proxy for "stuff that works".

[hadley]

Yeah, should definitely be CRAN. If you want to be on the bleeding edge, you should have to jump through a few hoops.

[cboettig]

Sounds good, thanks!

(@eddelbuettel For some projects the master branch is the stable deployment branch of a project and not necessarily more dynamic than what's on CRAN. I developed this use case with an ropensci:dev image mostly so I'd have quick access to the CRAN versions so just thought I'd check).