3.1.0 beta packages overwrote the 3.0.3 debian precise packages.

summary.lm does not compute correct statistics for weighted regression

quantile over repeated floating point bug

Different Results for Ri386 3.0.2 and Rx64 3.0.2 on Windows 7 64-bit

read.csv is converting numerics with many decimals to factors or characters

anomoly in parsing hexadecimal constants ending with "p-<n>L".

R CMD INSTALL --build reports creating a file with the wrong name (extra .gz at end)

defunct .find.packages call in package.manager() function

Calling parse() on attached R file crashes R

readLines() corrupts UTF-8 characters on Windows with open connections

lag() does not give a time series as output

R converts data from float to string when there are too many decimal places

strptime() rejects +1300 time-zone offset

sample: Walker's alias method threshold is 200, not 250

While in browse environment entered from Step Into, every function call is debugged

R 3.1.0 didn't work properly with gstat package

WISHLIST: modify behavior of (C entry point) nrows to handle data.frames

addition should return NA and integer overflow warning, but does not when compiled with clang

vignette creation fails silently if VignetteBuilder is not installed

Parallel routines creates files in /dev/shm that upset rkhunter

chull() fails if both x and y contain NAs at the first or last index

Sweave's \Sexpr misses expressions with backslashes

options(foo = NULL) does not return the previous value

(semi-)transparent "grid" elements disappear in the graphics device upon resizing

Function graphics::curve fails for some functions that do not vectorize regularly

hist function does not give consistent and accurate results with plot=FALSE

txtProgressBar displays erratically when run in parallel under many cores

Possible omission or incorrect documentation for "R CMD config --ldflags"

Using -L and -lR in own build finds wrong library

power.t.test fails when required N > 1e7

doMouseEvent calculates the wrong vector to return

system(..., intern=FALSE) will report success even if the syscall failed