|
1 | 1 | # CRAN Submission History |
2 | 2 |
|
3 | | -## v 0.2.1 - Submission 3 - (November 1st, 2018) |
| 3 | +## v 0.3.0 |
4 | 4 |
|
5 | | -This is a minor release to address a bug with the `report_path` parameter of `CreatePackageReport`. Prior to this fix, reports would continue to be saved to a default location rather than the file path supplied by the user. |
| 5 | +### Submission on December 19th, 2018 |
| 6 | +> This is a major release with several improvements to |
| 7 | +> R package diagnostics, report layout, and testing |
| 8 | +> strategy. New features and changes are now being |
| 9 | +> tracked in NEWS.md. |
| 10 | +> |
| 11 | +> This NEWS.md file and all |
| 12 | +> source code is maintained at https://github.com/UptakeOpenSource/pkgnet. |
| 13 | + |
| 14 | +### CRAN Response on December 20th, 2018 (Paraphrased) |
6 | 15 |
|
7 | | -Other items in this release are typo corrections, some additional parameter checks, and more verbose error and info messages. |
| 16 | +> Dear maintainer, |
| 17 | +> |
| 18 | +> package pkgnet_0.3.0.tar.gz does not pass the incoming checks automatically, please see the following pre-tests: Windows (2 ERRORs) & Debian (1 ERROR) |
| 19 | +> |
| 20 | +> ... |
| 21 | +> |
| 22 | +> Please fix all problems and resubmit a fixed version via the webform. |
| 23 | +> |
| 24 | +> ... |
| 25 | +> |
| 26 | +> Best regards, |
| 27 | +> CRAN teams' auto-check service |
8 | 28 |
|
9 | | -## v 0.2.0 - Submission 2 - (April 30th, 2018) |
| 29 | +See [#154](https://github.com/UptakeOpenSource/pkgnet/pull/154) for the issue description and fix. |
| 30 | + |
| 31 | +### Resubmission on December 20th, 2018 |
| 32 | +> The attached package addresses issues found earlier today in the CRAN teams' auto-check service. It has been checked (via R CMD check --as-cran) on both R-core and R-devel versions today. |
| 33 | +> |
| 34 | +> This NEWS.md file and all source code is maintained at https://github.com/UptakeOpenSource/pkgnet. |
| 35 | +
|
| 36 | +### CRAN response on December 21st (Paraphrased) |
| 37 | +>Dear maintainer, |
| 38 | +> |
| 39 | +>package pkgnet_0.3.0.tar.gz does not pass the incoming checks automatically, please see the following pre-tests: |
| 40 | +Windows: ... |
| 41 | +Status: 1 ERROR |
| 42 | +... |
| 43 | +Warning: invalid package 'd:/RCompile/CRANincoming/R-devel/pkgnet.Rcheck/tests_i386' |
| 44 | +... |
| 45 | +Best regards, |
| 46 | +CRAN teams' auto-check service |
| 47 | +Flavor: r-devel-linux-x86_64-debian-gcc, r-devel-windows-ix86+x86_64 |
| 48 | + |
| 49 | +### Resubmission on January 2nd, 2019 |
| 50 | +>Hello, |
| 51 | +> |
| 52 | +>I hope you had a refreshing holiday break. |
| 53 | +> |
| 54 | +>Apologies for the past issues with this build. I believe we have remedied the functionality that did not pass i386 tests. However, I cannot confirm this as the last submission alsopassed R CMD check on R-devel without issue. Is there a separate docker container I can use to check i386 compatibility? |
| 55 | +> |
| 56 | +>This submission passes R CMD check tests on r-devel with two warnings regarding URLs that fail within the container but have been confirmed valid and pass on R CMD check on R-core outside the container. |
| 57 | +> |
| 58 | +>Here is the version info: |
| 59 | +``` |
| 60 | +> RD CMD check --as-cran pkgnet_0.3.0.tar.gz |
| 61 | +* using log directory ‘/RPackage/pkgnet.Rcheck’ |
| 62 | +* using R Under development (unstable) (2018-12-21 r75875) |
| 63 | +* using platform: x86_64-pc-linux-gnu (64-bit) |
| 64 | +... |
| 65 | +``` |
| 66 | +> |
| 67 | +>The exact procedure I followed is outlined here: https://alexandereckert.com/post/testing-r-packages-with-latest-r-devel/ |
| 68 | +> |
| 69 | +>All source code is maintained at https://github.com/UptakeOpenSource/pkgnet. |
| 70 | +> |
| 71 | +>Sincerely, |
| 72 | +> |
| 73 | +>Brian Burns (current pkgnet maintainer) |
| 74 | +
|
| 75 | +### Response on January 2nd, 2019 |
| 76 | + |
| 77 | +>Dear maintainer, |
| 78 | +> |
| 79 | +>thanks, package pkgnet_0.3.0.tar.gz is on its way to CRAN. |
| 80 | +> |
| 81 | +>Best regards, |
| 82 | +CRAN teams' auto-check service |
| 83 | +Flavor: r-devel-linux-x86_64-debian-gcc, r-devel-windows-ix86+x86_64 |
| 84 | +Check: CRAN incoming feasibility, Result: Note_to_CRAN_maintainers |
| 85 | + Maintainer: 'Brian Burns <brian.burns@uptake.com>' |
| 86 | + |
| 87 | +--- |
| 88 | + |
| 89 | +## v 0.2.1 |
| 90 | + |
| 91 | +### Submission on November 1st, 2018 |
| 92 | + |
| 93 | +>This is a minor release to address a bug with the `report_path` parameter of `CreatePackageReport`. Prior to this fix, reports would continue to be saved to a default location rather than the file path supplied by the user. |
| 94 | +
|
| 95 | +>Other items in this release are typo corrections, some additional parameter checks, and more verbose error and info messages. |
| 96 | +
|
| 97 | +--- |
| 98 | + |
| 99 | +## v 0.2.0 |
| 100 | + |
| 101 | +### Submission on April 30th, 2018 |
10 | 102 | * Resubmitted to CRAN without test folder or source vigette code. |
11 | 103 | * This was to ensure nothing is written outside of the temp folder |
12 | 104 | during vignette build or package testing. |
13 | 105 | * Future versions will handle this issue more directly. |
14 | 106 |
|
15 | | -## v0.1.0 - Submission 1 - (April 11, 2018) |
| 107 | +---- |
| 108 | + |
| 109 | +## v0.1.0 |
| 110 | + |
| 111 | +### Submission on April 12, 2018 |
16 | 112 |
|
17 | | -### R CMD check results |
| 113 | +#### R CMD check results |
| 114 | +* No issues |
| 115 | + |
| 116 | +#### CRAN Response |
| 117 | +* accepted and available on CRAN |
| 118 | + |
| 119 | +### Submission on April 11, 2018 |
| 120 | + |
| 121 | +#### R CMD check results |
18 | 122 | * One NOTE about license file, will see what they say |
19 | 123 |
|
20 | | -### CRAN Response |
| 124 | +#### CRAN Response |
21 | 125 | * Need to use CRAN recognized LICENSE format |
22 | 126 | * Need to single-quote `pkgnet` in `DESCRIPTION` file |
23 | 127 |
|
24 | | -## v0.1.0 - Submission 2 - (April 12, 2018) |
25 | 128 |
|
26 | | -### R CMD check results |
27 | | -* No issues |
28 | | - |
29 | | -### CRAN Response |
30 | | -* accepted and available on CRAN |
|
0 commit comments