----- Original Message ----- > From: "Gabe Becker" <becker.g...@gene.com> > To: bioc-devel@r-project.org, "Jim Fitzgerald" <fitzgerald.ja...@gene.com> > Sent: Thursday, October 30, 2014 10:21:17 AM > Subject: [Bioc-devel] R-devel update schedule/strategy for Bioc devel build > machines > > Bioc admins, > > We have an automatic build/test mechanism for our internal packages > which > we'd like to match the Bioc build machines as closely as possible. > AFAIU, > the exact commit-specific version of R-devel used on your devel build > server changes occasionally within Bioc releases, and we'd like to > mirror > those changes on our system. > > Is there a set schedule for when the exact commit of R-devel on your > build > server changes?
No. We do it in response to the following events: - significant changes in the R code - "seems like a while since we last updated R" - milestones leading up to release (release candidates, alpha, beta, etc). You could scrape the build report daily to see if the version of R has changed. Also, do you guys grab them as tarballs, or > checkout/update > from the svn? Tarballs. Dan > > Thanks, > ~G > > -- > Computational Biologist > Genentech Research > > [[alternative HTML version deleted]] > > _______________________________________________ > Bioc-devel@r-project.org mailing list > https://stat.ethz.ch/mailman/listinfo/bioc-devel > _______________________________________________ Bioc-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/bioc-devel
