Skip to content

Upgrade to plotly.js v1.54.1 #1771

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

Merged
merged 6 commits into from
May 19, 2020
Merged

Upgrade to plotly.js v1.54.1 #1771

merged 6 commits into from
May 19, 2020

Conversation

cpsievert
Copy link
Collaborator

No description provided.

@cpsievert cpsievert mentioned this pull request May 18, 2020
@cpsievert cpsievert merged commit c5beddf into master May 19, 2020
@nicolaskruchten
Copy link

Awesome! I'm glad we finally got this "Plotly team submits the PR" process run through once :)

You can expect a follow-up PR for 1.54.2 in the coming days, and then 1.55.0 will come out in a few weeks. No new trace types are expected for a while, so hopefully this process remains smooth.

@cpsievert what's your approach towards CRAN and release announcements? What we like to do with Plotly.py is that every time we write up the docs at plotly.com/python for the new features, we do a Community Forum post like these ones. We recently "caught up" on the R side with our docs and belatedly put out this post as a "roundup". So now that there are new features in Plotly.R since that post, @jdamiba will port the Python docs (for unified hover, range breaks and shape drawing, basically) over to plotly.com/r and do another forum post to announce the new features (probably after 1.54.2 is merged). If that could be synced with a CRAN update that's cool but I don't see it as critical, just curious about your thoughts :)

@cpsievert
Copy link
Collaborator Author

It's best to be somewhat conservative about CRAN releases -- I usually aim for about a 2 month release cycle (unless critical patch fixes surface, of course)

@nicolaskruchten
Copy link

OK cool. Nothing critical is in the works ATM :) Would appreciate a retweet on the community forum post when it comes out!

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

Successfully merging this pull request may close these issues.

2 participants