Skip to content

Conversation

mjankowski
Copy link
Contributor

This message is sort of long, and it seems unlikely that people who are upgrading are not upgrading all the way to latest?

I'd probably just remove this entirely (in favour of release notes, changelogs, upgraders reviewing upstream first, etc) but short of that, maybe reduce length...?

@rosa
Copy link
Member

rosa commented Dec 27, 2024

@mjankowski, now it might be the moment to remove it, yeah, but it's so verbose because people would ignore it and run into all sorts of problems when upgrading from < 0.8. It's been a while, so yeah, it should be fine I hope. In my short experience, people don't read the release notes, the changelog or review anything upstream before upgrading, so it's better to be as loud as possible 😅 🤷

@mjankowski mjankowski force-pushed the gemspec-upgrade-reduce branch from b61c4eb to 9d31f06 Compare December 27, 2024 20:16
@rosa
Copy link
Member

rosa commented Dec 28, 2024

Thank you so much, @mjankowski! 🙏

@rosa rosa merged commit eedb4fe into rails:main Dec 28, 2024
4 checks passed
@mjankowski mjankowski deleted the gemspec-upgrade-reduce branch December 28, 2024 16:56
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