Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Is there a reason to require R ≥ 3.4.1? #16

Closed
jbkunst opened this issue Sep 27, 2017 · 4 comments
Closed

Is there a reason to require R ≥ 3.4.1? #16

jbkunst opened this issue Sep 27, 2017 · 4 comments

Comments

@jbkunst
Copy link

@jbkunst jbkunst commented Sep 27, 2017

Hi @wilkox

Thanks for the package!

Is there a reason to require the last R version? Sometimes upgrade R have a big cost (for example when you teach R in a lab).

Thanks,

@wilkox
Copy link
Owner

@wilkox wilkox commented Oct 2, 2017

Hi @jbkunst. Thanks for raising this. I've had other requests by email to reduce the version requirement so obviously this is an issue for many people. I'm going to try and reduce the requirement for treemapify and ggfittext to R ≥ 3.1, but I want to do some more testing first.

@tiernanmartin
Copy link

@tiernanmartin tiernanmartin commented Nov 15, 2017

Any update on this?

@wilkox
Copy link
Owner

@wilkox wilkox commented Nov 15, 2017

I'm working on getting an R ≥ 3.1-tested version of ggfittext (which is upstream of this package) onto CRAN. Once that's done I can submit a similar treemapify update.

In the meantime the development version of treemapify works on ≥ 3.1 – you can try installing it with devtools::install_github('wilkox/treemapify').

@wilkox
Copy link
Owner

@wilkox wilkox commented Nov 18, 2017

treemapify v2.4.0 requiring R ≥ 3.1 is now available on CRAN.

@wilkox wilkox closed this as completed Nov 18, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants