4 ms·
Not happy? Do something about it: try release candidates, report bugs, and help triage and fix reported bugs.
by thinkbohemian 14y ago
Not happy? Do something about it: try release candidates, report bugs, and help triage and fix reported bugs.
- calinet6 14y agoOk, yes, that's an extremely great and open-source way to handle this. But seriously, can we at least expect moderately stable releases? I do not think that's too much to ask, especially for a framework which has, in the past, achieved that.
- foobar2k 14y agoI completely agree with this. We (bugsnag) are running on rails 4 beta right now to help iron out any production issues before that is released. We didn't, however, realize that "patch" releases also have release candidates. I'd recommend following the rails blog (http://weblog.rubyonrails.org/ http://weblog.rubyonrails.org/) which announces release candidate builds too.
- thibaut_barrere 14y agoThanks for the blog post - and I didn't realize that patch releases also had RC. It looks like this release was quite fat, for a patch release. I added "check rails diff" to my deploy todo list. EDIT: I just noticed that http://weblog.rubyonrails.org/ http://weblog.rubyonrails.org/ doesn't have a way to subscribe by email. I signed-up by email with this site instead http://blogtrottr.com http://blogtrottr.com, in case it helps other here.
- thinkbohemian 14y agoYou can also subscribe to the rails-core mailing list, all betas, RC and full releases get announced there.
- thibaut_barrere 14y agoThere's quite a bit more discussions on rails-core apart from RC and releases, so subscribing to the blog is a good idea if your time is limited :-)