|
1 | 1 | ## Test environments |
2 | | -* local OS X install, R 3.1.2 |
3 | | -* ubuntu 12.04 (on travis-ci), R 3.1.2 |
| 2 | +* local OS X install, R 3.2.0 |
| 3 | +* ubuntu 12.04 (on travis-ci), R 3.2.0 |
4 | 4 | * win-builder (devel and release) |
5 | 5 |
|
6 | 6 | ## R CMD check results |
7 | 7 | There were no ERRORs, WARNINGs or NOTEs. |
8 | 8 |
|
9 | 9 | ## Downstream dependencies |
10 | 10 | This release changes the backend of stringr from R's built in regular |
11 | | -expression engine to use instead use ICU's, as provided by the stringi |
12 | | -package. The potential for backward incompatible changes was high so I have |
13 | | -R CMD check on all 155 downstream dependencies |
14 | | -(https://github.com/hadley/stringr/blob/master/revdep/summary.md). As well |
15 | | -as carefully reviewing the results, I notified all downstream maintainers |
16 | | -of the pending change in early Dec and again on April 14. |
| 11 | +expression engine to ICU's, as provided by the stringi package. The potential |
| 12 | +for backward incompatible changes was high so I have R CMD check on all 158 |
| 13 | +downstream dependencies (https://github.com/hadley/stringr/blob/master/revdep/summary.md). |
| 14 | + |
| 15 | +All downstream maintainers (both en masse, and individually in the case of |
| 16 | +problems) were notified of the change in early Dec and again on April 14 |
| 17 | +(two weeks ago). |
| 18 | + |
| 19 | +Despite these warnings, I have identifed six packages that now fail R CMD |
| 20 | +check with either an error or a warning: |
| 21 | + |
| 22 | +* Errors: CSS, mpoly, NMF, pathological, rlme |
| 23 | +* Warnings: MazamaSpatialUtils |
| 24 | + |
| 25 | +Two other packages failed with non-installed-related errors (RSiteCatalyst, |
| 26 | +REDCapR). Judging from the error messages, I don't believe these failures |
| 27 | +at related to stringr. |
0 commit comments