Per our regular schedule, a new release is due next week. The main branch in the repo is ready: what I labeled as 1.0.14.16 just had another round of reverse-dependency checks which passed without issue (see repo rcpp-log for the usual details).
As per our discussions around (meta) issue #1365 we will name this one as 1.1.0. The diff isready, and I may commit it and then just update the date to July 1 (or whichever day it ends up being). Or I may just wait and open the PR once it is under processing at CRAN as in the past. There is not much of a practical difference: 1.0.14.16 is effectively 1.1.0, apart from cosmetics in DESCRIPTION, ChangeLog, NEWS and so on.
Per our regular schedule, a new release is due next week. The main branch in the repo is ready: what I labeled as 1.0.14.16 just had another round of reverse-dependency checks which passed without issue (see repo rcpp-log for the usual details).
As per our discussions around (meta) issue #1365 we will name this one as 1.1.0. The diff isready, and I may commit it and then just update the date to July 1 (or whichever day it ends up being). Or I may just wait and open the PR once it is under processing at CRAN as in the past. There is not much of a practical difference: 1.0.14.16 is effectively 1.1.0, apart from cosmetics in DESCRIPTION, ChangeLog, NEWS and so on.