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

update rails version for earlier releases in edgeguides #17504

Merged
merged 1 commit into from Nov 4, 2014

Conversation

Gaurav2728
Copy link
Contributor

No description provided.

zzak pushed a commit that referenced this pull request Nov 4, 2014
update rails version for earlier releases in edgeguides [ci skip]
@zzak zzak merged commit 061687c into rails:master Nov 4, 2014
@JuanitoFatas
Copy link
Contributor

@Gaurav2728 @zzak Should be 4.1.7, 3.2.20, 4.0.11.

@zzak
Copy link
Member

zzak commented Nov 4, 2014

@JuanitoFatas For whatever reason, those versions aren't available on guides.rubyonrails.org yet.. :(

@Gaurav2728
Copy link
Contributor Author

@JuanitoFatas
Copy link
Contributor

Previous discussion of Automation PR is here: #14996

@zzak
Copy link
Member

zzak commented Nov 4, 2014

@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.

@JuanitoFatas
Copy link
Contributor

👍 😄

@Gaurav2728
Copy link
Contributor Author

@zzak @JuanitoFatas Thanks. I'll follow the Automation process discussed in that PR 💛

@rafaelfranca
Copy link
Member

O_O, those versions should be on guides. Let me fix this.

@rafaelfranca
Copy link
Member

Fixed. The documentation generation lock was acquired since October 3 and never released. We are not generating our docs since that date. 😢

@rafaelfranca
Copy link
Member

cc @fxn

@fxn
Copy link
Member

fxn commented Nov 4, 2014

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).

@fxn
Copy link
Member

fxn commented Nov 4, 2014

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.

@zzak
Copy link
Member

zzak commented Nov 4, 2014

Thanks for fixing it @rafaelfranca <3 <3 <3

@fxn
Copy link
Member

fxn commented Nov 11, 2014

Just added that sanity job to the crontab of the docs server.

@Gaurav2728 Gaurav2728 deleted the gaurav-update_edgeguide branch March 20, 2015 07:04
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.

None yet

5 participants