-
Notifications
You must be signed in to change notification settings - Fork 36
Commit
- Loading branch information
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,5 +1,7 @@ | ||
# uptasticsearch development version | ||
|
||
# uptasticsearch 0.4.0 | ||
|
||
## Features | ||
|
||
### Added support for ES7.x | ||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -9,7 +9,7 @@ | |
* local Windows 10, R 3.3.2 | ||
* Windows via `devtools::build_win()` | ||
|
||
### R CMD check results | ||
### `R CMD check` results | ||
* 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. | ||
|
||
|
@@ -30,31 +30,31 @@ | |
|
||
## v0.1.0 - Submission 1 - (August 28, 2017) | ||
|
||
### R CMD check results | ||
### `R CMD check` results | ||
* No issues | ||
|
||
### CRAN Response | ||
* Need to use CRAN canonical form (http://cran.r-project.org/package=uptasticsearch) | ||
|
||
## v0.1.0 - Submission 2 - (August 28, 2017) | ||
|
||
### R CMD check results | ||
### `R CMD check` results | ||
* No issues | ||
|
||
### CRAN Response | ||
* CRAN canonical form uses HTTPS (https://cran.r-project.org/package=uptasticsearch) | ||
|
||
## v0.1.0 - Submission 3 - (August 29, 2017) | ||
|
||
### R CMD check results | ||
### `R CMD check` results | ||
* No issues | ||
|
||
### CRAN Response | ||
* CRAN URLs are still missing HTTPS (submitter error) | ||
|
||
## v0.1.0 - Submission 4 - (August 29, 2017) | ||
|
||
### R CMD check results | ||
### `R CMD check` results | ||
* No issues | ||
|
||
### CRAN Response | ||
|
@@ -63,48 +63,71 @@ | |
|
||
## v0.1.0 - Submission 5 - (August 29, 2017) | ||
|
||
### R CMD check results | ||
### `R CMD check` results | ||
* No issues | ||
|
||
### CRAN Response | ||
* No lingering issues. v0.1.0 released to CRAN! | ||
|
||
## v0.2.0 - Submission 1 - (April 12, 2018) | ||
|
||
### R CMD check results | ||
### `R CMD check` results | ||
* No issues | ||
|
||
### CRAN Response | ||
* No issues. v0.2.0 released to CRAN! | ||
|
||
## v0.3.0 - Submission 1 - (June 18, 2018) | ||
|
||
### R CMD check results | ||
### `R CMD check` results | ||
* No issues | ||
|
||
### CRAN Response | ||
* No issues. v0.3.0 released to CRAN! | ||
|
||
## v0.3.1 - Submission 1 - (January 28, 2019) | ||
|
||
### R CMD check results | ||
### `R CMD check` results | ||
* 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. | ||
|
||
### CRAN Response | ||
* Upload a new version with this fixed or your package comes down in 7 days | ||
|
||
## v0.3.1 - Submission 2 - (January 29, 2019) | ||
|
||
### R CMD check results | ||
### `R CMD check` results | ||
* Empty links in `NEWS.md` | ||
|
||
### CRAN Response | ||
* Upload a new version with this fixed or your package comes down in 7 days | ||
|
||
## v0.3.1 - Submission 3 - (January 30, 2019) | ||
|
||
### R CMD check results | ||
### `R CMD check` results | ||
* No issues | ||
|
||
### CRAN Response | ||
* No issues. v0.3.1 released to CRAN! | ||
|
||
## v0.4.0 - Submission 1 - (September 9, 2019) | ||
|
||
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]) | ||
### `R CMD check` results | ||
* No issues | ||
|
||
### CRAN Response | ||
* 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. | ||
|
||
## v0.4.0 - Submission 1 - (September 11, 2019) | ||
|
||
### `R CMD check` results | ||
* No isses | ||
|
||
### CRAN Response | ||
* No issues. v0.4.0 released to CRAN! |
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,4 +1,4 @@ | ||
pandoc: 1.19.2.1 | ||
pandoc: 2.3.1 | ||
pkgdown: 1.3.0 | ||
pkgdown_sha: ~ | ||
articles: | ||
|
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.