Skip to content

Commit

Permalink
Changes in prep for first v0.1.1 CRAN submission
Browse files Browse the repository at this point in the history
  • Loading branch information
brews committed Aug 26, 2016
1 parent d6477f6 commit c5260b7
Show file tree
Hide file tree
Showing 4 changed files with 4 additions and 12 deletions.
2 changes: 1 addition & 1 deletion .Rbuildignore
Original file line number Diff line number Diff line change
Expand Up @@ -4,4 +4,4 @@
^.*\.sublime-workspace$
^.*\.sublime-project$
^data-raw$
^cran-comments\.md$
^cran-comments\.md$
2 changes: 1 addition & 1 deletion DESCRIPTION
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
Package: burnr
Title: Advanced Fire History Analysis in R
Version: 0.1.1.9000
Version: 0.1.1
Authors@R: c(
person("Steven", "Malevich", email = "[email protected]", role = c("aut", "cre")),
person("Christopher", "Guiterman", role = c("ctb")),
Expand Down
2 changes: 1 addition & 1 deletion NEWS.md
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
# burnr v0.1.1.9000
# burnr v0.1.1

Changes in this patch:

Expand Down
10 changes: 1 addition & 9 deletions cran-comments.md
Original file line number Diff line number Diff line change
@@ -1,18 +1,10 @@
## Resubmission

This is a resubmission. In this version, I put a space between a URL and an escaped bracket in the vignette file 'introduction.Rmd'. R CMD now no longer detects this as a faulty URL.

Note also that the possibly mis-spelled word in DESCRIPTION, 'FHX', is not a misspelling.

## Test environments
* local Ubuntu & OS X install, R release
* travis-ci: Ubuntu 12.04 (devel, release, and R 3.2.5) and OSX (R release)
* win-builder (devel)

## R CMD check results
There were no ERRORs, WARNINGs.

One NOTE mentions that this is the first time this package has been submitted to CRAN.
There were no ERRORs, WARNINGs. There is one NOTE on "checking CRAN incoming feasibility".

## Downstream dependencies
This package has no downstream dependencies.

0 comments on commit c5260b7

Please sign in to comment.