CRAN-ready for 1.0.0

[lorenzwalthert]

• Get rid of notes.
• Consider changing api tests to not format in temp dir since it creates problems with appveyor.
• Make tests passing quickly enough?
• Wait for krlmlr/utf8 to be released on CRAN and remove Remotes: in DESCRIPTION
• Clarify LICENCE with usethis()? (Link)
• Completing cran-release-notes.md
• Update NEWS.md (describe every exported function in order of relevance, see pillar).
• Create a pre-release.
• Bump version to 0.1.0
• devtools::check_spelling()
• Delete all man files for unexported functions.
• Make sure every man page of exported functions has an example.

[lorenzwalthert]

@krlmlr What else do we need to do here?

[krlmlr]

We need to release utf8. How long are the tests running, will this be a problem for CRAN?

[lorenzwalthert]

It takes about one minute on my machine. In the CRAN Submission Policy it only says:

Checking the package should take as little CPU time as possible, as the CRAN check farm is a very limited resource and there are thousands of packages. Long-running tests and vignette code can be made optional for checking, but do ensure that the checks that are left do exercise all the features of the package.

So I don't really know what that means but I think one minute is too much. Can we define a few tests that cover all rules?

[hadley]

A minute should be ok

[lorenzwalthert]

@krlmlr can you tell me whether we need to further specify the licence (see this link)?