On 3/15/16 3:52 AM, Martin Maechler wrote:
Following up on Lukas's explanatory message, we will try to sync up with R releases on a more regular schedule from now on, even if we don't actually push FastR based on that version. So we should discover test regressions earlier.peter dalgaard <pda...@gmail.com> on Sat, 12 Mar 2016 19:11:40 +0100 writes:> OK, .Internal is not necessary to reproduce oddity in this area. I also see things like (notice 1980) >> strptime(paste0(sample(1900:1999,80,replace=TRUE),"/01/01"), "%Y/%m/%d", tz="CET") ...............> The issue seems to be present in R-devel but not in (CRAN) 3.2.0 nor in R 3.2.3 (and earlier), but indeed unfortunately in 3.2.4. This has been fixed now in "R 3.2.4 patched" (and R-devel of course). Thank you Mick, for the report... ... ... though I "must" add: If you do have your own tests / checks (as you said in the OP) and are company as big as Oracle using the free (in the full sense of "speech" *and* "beer") software R, it would be *really* *really* courteous if you did run your test suite when we announce and release betas or release candidates ("RC") (and in the case of the upcoming yearly release in April, even "alphas" before them) so we, the R community and the R core developers could find bugs *before* release.
Mick ______________________________________________ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel
