- Alpine 3.5 (on Jenkins CI), R 3.4.0
- local CentOS 7.3, R 3.4.0
- local OS X, R 3.3.2
- local Windows 10, R 3.3.2
- Windows via
devtools::build_win()
- There were no ERRORs, WARNINGs.
- One NOTE from
checking CRAN incoming feasibility ...can be safely ignored since it's a note that notifies CRAN that this is a new maintainer/submission.
- Automatic checking upon CRAN submission yielded two notes. One was the "incoming feasbility..." item we mentioned above, which is not an issue.
- The other note said that
Author field differs from that derived from Authors@R. This did not arise when runningR CMD check --as-cranlocally, but it looks like "fnd" is not a supported tag for an author. Removed that tag.
- Need to use the CRAN preferred method of declaring the BSD 3-Clause license
- Need to quote software names
- No lingering issues. v0.0.2 released to CRAN!
- No issues
- Need to use CRAN canonical form (http://cran.r-project.org/package=uptasticsearch)
- No issues
- CRAN canonical form uses HTTPS (https://cran.r-project.org/package=uptasticsearch)
- No issues
- CRAN URLs are still missing HTTPS (submitter error)
- No issues
- Still missing HTTPS in CRAN URLs (we'd been editing the README at the repo root, not the one built with the package)
- Reviewers asked if examples in "\dontrun" could be run instead
- No issues
- No lingering issues. v0.1.0 released to CRAN!
- No issues
- No issues. v0.2.0 released to CRAN!
- No issues
- No issues. v0.3.0 released to CRAN!
- Issues on several platforms, of the form
premature EOF.... This is a result of forgetting to put the test data in the package tarball before upload.
- Upload a new version with this fixed or your package comes down in 7 days
- Empty links in
NEWS.md
- Upload a new version with this fixed or your package comes down in 7 days
- No issues
- No issues. v0.3.1 released to CRAN!
In this submission, we changed maintainer from [email protected] to [email protected]. Added this note in the initial submission:
This is a release to add support for Elasticsearch 7.x, a major release stream that has been General Availability since April 2019.
You may see that the maintainer email is changing from "[email protected]" to "[email protected]". This is a contact info update only, not an actual maintainer change. The "uptake.com" address is tied to the company that holds copyright over this project (https://github.com/uptake/uptasticsearch/blob/master/LICENSE#L3). I no longer work there but have received their permission to continue on as the maintainer. If you need confirmation you can contact my coauthors who still work there ([email protected], [email protected]) or that company's legal team ([email protected])
- No issues
- Release was auto-accepted, but the response email said "We are waiting for confirmation from the old maintainer address now.". I responded and re-iterated the message above about changed maintainer email. No response yet. We are blocked until they respond.
- CRAN seems ok with the maintainer change, noted that we have one bad link in
README.md, "./CONTRIBUTING.md". Needs to be changed to a fully-specified URL.
- No isses
- No issues. v0.4.0 released to CRAN!