Minimal set of changes to permit master to be 1.17.99

[eddelbuettel]

Congratulations on getting 1.17.0 onto CRAN.

As with previous releases, master lags as is still at 1.16.99 in DESCRIPTION and src/init.c (plus some .po files I left alone). Feel free to add to the PR as needed.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 98.64%. Comparing base (4b3a081) to head (98c68d9).
Report is 1 commits behind head on master.

Additional details and impacted files

@@           Coverage Diff           @@
##           master    #6829   +/-   ##
=======================================
  Coverage   98.64%   98.64%           
=======================================
  Files          79       79           
  Lines       14642    14642           
=======================================
  Hits        14444    14444           
  Misses        198      198           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[TysonStanley]

Thanks @eddelbuettel, didn't get this in last night after it was accepted, thanks for getting it started. @MichaelChirico this should be all the files that are needed to bump to 1.17.99

[MichaelChirico]

atime & lintr failures are OK. Latter is due to some improved logic just landed upstream, will fix that separately.

thanks!

[MichaelChirico]

@TysonStanley maybe the procedure should be to push an "as-submitted" release branch, then anyone who sees it hit CRAN can merge async, WDYT?

of course if it's rejected, the PR can be deleted

[TysonStanley]

I'm open to that since the process is a bit prolonged and often ends in the evening or middle of the night.