Skip to content

Commit

Permalink
Update NEWS.md and cran-comments.md
Browse files Browse the repository at this point in the history
Merge branch 'CR'

# Conflicts:
#	NEWS.md
  • Loading branch information
maurolepore committed May 24, 2019
2 parents 679e32c + 676d5d3 commit 553115d
Show file tree
Hide file tree
Showing 2 changed files with 3 additions and 35 deletions.
36 changes: 2 additions & 34 deletions NEWS.md
Original file line number Diff line number Diff line change
@@ -1,39 +1,7 @@
# fgeo 1.1.3

# fgeo (development version)

* Work in progress.

# fgeo 1.1.3 ([GitHub](https://github.com/forestgeo/fgeo/releases))

* First CRAN release.

# fgeo 1.1.2 ([GitHub](https://github.com/forestgeo/fgeo/releases) and [drat](https://forestgeo.github.io/drat/))

This release marks that all __fgeo__ packages now meet CRAN standards. [Most changes are internal](../CHANGELOG.html), and focused on making __fgeo__ more reliable and easier to maintain.

* The required R version is now >= 3.2.

* When running `library(fgeo)`, error messages are now clearer when __fgeo__ dependencies are outdated.

Many thanks to those who [reviewed](https://forestgeo.github.io/fgeo/authors.html) __fgeo__ for your contribution in making it better.

# fgeo 1.1.1 ([GitHub](https://github.com/forestgeo/fgeo/releases))

* Meet CRAN standards.

* Use tidy versions.

# fgeo 1.1.0 ([GitHub](https://github.com/forestgeo/fgeo/releases))

* Import fgeo packages via `Additional_repositories` served at <https://forestgeo.github.io/drat/>

# fgeo 1.0.1 ([GitHub](https://github.com/forestgeo/fgeo/releases))

* Style.

* Tidy dependencies.

# fgeo 1.0.0 ([GitHub](https://github.com/forestgeo/fgeo/releases))
# fgeo 1.1.3

* Internal release.
* First release on CRAN.
2 changes: 1 addition & 1 deletion cran-comments.md
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@

## R CMD check results

0 errors | 1 warnings | 0 notes
0 errors | 0 warnings | 1 notes

New submission

Expand Down

0 comments on commit 553115d

Please sign in to comment.