Next CRAN release

[jgabry]

I'd like to do another CRAN release relatively soon so that the parallel coordinates plot is available. We use it in a paper that just went up on arXiv so it would be nice to get that in the CRAN version before too long.

Here's my checklist of things to do before the release:

• Get the mcmc_parcoord PR merged as soon as everyone is happy with it (Introduce mcmc_parcoord #108)
• Update the NEWS file with stuff that's already been added since previous release (several _data functions that @tjmahr added, some minor fixes, etc.)
• Add @tjmahr to the DESCRIPTION file
• Fix Error when plotting values for a corr_matrix with mcmc_rhat #105 (looks like @tjmahr is on top of this)
• Add divergences to mcmc_scatter (PR Divergences for mcmc_scatter #112)
• Check R release and R devel on win-builder
• Rebuild online doc

So not too much that needs to get done, but I might be forgetting something.

@tjmahr if you want to try get the mcmc_dens_ridges and similar functions in
for this next release that's fine too but I think it's also fine to wait for a subsequent
release if it would feel rushed to get them in for this one.

[tjmahr]

I think we need to iron out some final aesthetic tweaks for the mcmc_dens_ridges first. It can skip this release.

[jgabry]

Ok yeah probably best to wait on that.

…

On Thu, Sep 7, 2017 at 7:53 PM TJ Mahr ***@***.***> wrote: I think we need to iron out some final aesthetic tweaks for the mcmc_dens_ridges first. It can skip this release. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#109 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AHb4Q_dnYE0NOYHxKXP3cgqPB5WNqxgsks5sgIH3gaJpZM4PQNux> .

[jgabry]

@tjmahr If there's nothing you can think of that we should definitely put in the next release, then I'll go ahead start the release process. By that I mean I'll run R CMD CHECK again locally, then check on win-builder (release and devel), and assuming that's all fine I'll submit to CRAN and update the pkgdown documentation.

[tjmahr]

This sounds good!

[jgabry]

Actually I noticed there's something weird happening in Mac build from the last release on CRAN: https://www.r-project.org/nosvn/R.check/r-release-osx-x86_64/bayesplot-00check.html It seems to have resulted in the binary for El Capitan staying at v1.2 while for everything else it's v1.3: https://cran.r-project.org/web/packages/bayesplot/index.html It looks like there's an error in a test (that I can't reproduce locally) and a warning about pandoc. I thought the CRAN macs were up to date with pandoc but I guess maybe not.

…

On Fri, Sep 8, 2017 at 5:47 PM TJ Mahr ***@***.***> wrote: This sounds good! — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#109 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AHb4Q90gtRoZv38GJOeGmL4YW62pXirxks5sgbXtgaJpZM4PQNux> .

[jgabry]

Ok I think it's in ok enough shape for release. It passed fine on win-builder, locally my mac, and apparently a few times on travis. I just submitted. Will tag the release when accepted.

[jgabry]

@tjmahr Just tagged the release: https://github.com/stan-dev/bayesplot/releases/tag/v1.4.0