2.0.0 release checklist about civis-r HOT 6 CLOSED

I think we also want to run integration tests

from civis-r.

FYI, I've just checked with the develop branch of future - soon to be released, and dev-2.0 passes R CMD check --as-cran on my notebook(*). The main update there is that all 'condition' classes will be captured and relayed; previously only 'message' and 'warning' (+ 'error') were relayed.

(*) with the following constraint:

Generating API
The environmental variable CIVIS_API_KEY is not set. Add this to your .Renviron or call Sys.setenv(CIVIS_API_KEY = '<api_key>')
Generating API failed, reverting to default.

from civis-r.

We should be good to go!

from civis-r.

Hi, where are you guys when it comes to a CRAN release? Some guestimate for an ETA? I'm interested in rolling out a cleaned-up version of future, but that requires the #168 fix to be on CRAN.

from civis-r.

@patr1ckm how close do you think we are to releasing 2.0? Should we consider releasing 1.7 in the meantime to exposes #168?

from civis-r.

Close! I've been testing dev-2.0 on my machine for a few weeks, so we should be ready to go this week. I'll finish out the integration tests and tag you.

from civis-r.