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
update rails version for earlier releases in edgeguides #17504
Conversation
update rails version for earlier releases in edgeguides [ci skip]
@Gaurav2728 @zzak Should be 4.1.7, 3.2.20, 4.0.11. |
@JuanitoFatas For whatever reason, those versions aren't available on guides.rubyonrails.org yet.. :( |
@JuanitoFatas @zzak http://weblog.rubyonrails.org/2014/10/30/Rails_3_2_20_4_0_11_4_1_7_and_4_2_0_beta3_have_been_released/ 4.1.7, 3.2.20, 4.0.11 these are current released version. |
Previous discussion of Automation PR is here: #14996 |
@JuanitoFatas Thank you for that. In my opinion, we should at least maintain the most recent releases on this page "welcome". The rest of the pages I would consider unimportant. |
👍 😄 |
@zzak @JuanitoFatas Thanks. I'll follow the Automation process discussed in that PR 💛 |
O_O, those versions should be on guides. Let me fix this. |
Fixed. The documentation generation lock was acquired since October 3 and never released. We are not generating our docs since that date. 😢 |
cc @fxn |
Ouch, wonder what could we do to detect or auto-heal that. Everything in the docs server is thought so that it is autonomous (as much as possible). |
I believe we could have a cron job that checks the mtime of the lock file, if it is older than for example 1 or 2 hours we can consider the file to be stale and remove it. |
Thanks for fixing it @rafaelfranca <3 <3 <3 |
Just added that sanity job to the crontab of the docs server. |
No description provided.