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

Upgrade Rails #577

Open
MisterMartin opened this issue May 29, 2022 · 2 comments
Open

Upgrade Rails #577

MisterMartin opened this issue May 29, 2022 · 2 comments
Labels
upgrade upgrading gems/other packages

Comments

@MisterMartin
Copy link
Member

Should we upgrade rails for the next release? The current version is getting pretty old.

Perhaps upgrade for CHORDS v1.2?

@MisterMartin MisterMartin added the upgrade upgrading gems/other packages label May 29, 2022
@mdye
Copy link
Collaborator

mdye commented Feb 13, 2023

Any thoughts on which version or Rails we should update to at this point?

@MisterMartin
Copy link
Member Author

No explicit idea. I think the highest priorities are the dependabot gem updates (done) and fixing the highcharts problem. This are two high priority items on the Release 1.1 project. Perhaps put out a 1.1.0-rc2 now, so that this can be deployed to PAWS?

After that, should we finish all of the items on the Release 1.1 list and release it before upgrading Rails? Then make the rails upgrade a new project? On the other hand, it would be good to be starting the DEI deployment with an upgraded rails, and possibly upgraded influxdb and grafana?

Depends a lot on how much time we all have to work on this. I'm motivated to see CHORDS brought forward.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
upgrade upgrading gems/other packages
Projects
None yet
Development

No branches or pull requests

2 participants