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

Roxygen2 v7.1.0 bump #2685

Closed
istfer opened this issue Aug 20, 2020 · 3 comments
Closed

Roxygen2 v7.1.0 bump #2685

istfer opened this issue Aug 20, 2020 · 3 comments

Comments

@istfer
Copy link
Contributor

istfer commented Aug 20, 2020

We are but it may be time to change that. If someone wants to take it on before I can, the process is basically:

  • pick a date for the update and warn everyone
  • ideally close out as many open PRs as possible before then, to minimize merge conflicts
  • install the newest Roxygen on your dev machine
  • git pull, make sure your tree is clean, then make clean && make document
  • commit all the changed Rd and DESCRIPTION files
  • grep -R 7.0.2 . -> review, update appropriately, commit. I think at least three scripts scripts/travis/install.sh, .github/workflows/styler-actions.yml, and docker/depends/Dockerfile will need updating, but I may be forgetting others.
  • push, review, merge
  • remind everyone to update Roxygen on their own machine
  • monitor PRs for merge conflicts/accidental reversions (if it edits 300 files, it's probably an accidental reversion)

Originally posted by @infotroph in #2672

@istfer
Copy link
Contributor Author

istfer commented Aug 20, 2020

Just created this issue so that @infotroph's helpful comment doesn't get buried.

It would be nice if we can move from 7.0.2 to the most up-to-date version of Roxygen similar to what has been done before

@github-actions
Copy link

This issue is stale because it has been open 365 days with no activity.

@Aariq
Copy link
Collaborator

Aariq commented Jan 5, 2023

Currently using v7.1.2 of roxygen2 so closing this

@Aariq Aariq closed this as completed Jan 5, 2023
@infotroph infotroph mentioned this issue Feb 4, 2023
13 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants