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

"How often is reference built and replaced on website?" should be in the README #38

Open
mrhota opened this issue Apr 7, 2017 · 6 comments
Labels
Enhancement Improvement in a non-prose section of the book Meta Non-content issues (procedure, tooling, website, etc.)

Comments

@mrhota
Copy link
Contributor

mrhota commented Apr 7, 2017

It seems like it doesn't happen as often as https://doc.rust-lang.org/nightly/reference/ might lead you to expect.

@petrochenkov
Copy link
Contributor

This is one of a number of "improvements" brought by moving the reference into a separate submodule.
Now the nightly reference is updated when someone sends a PR updating that submodule to the main repo, get it merged, and the next nightly happens.

@steveklabnik
Copy link
Member

That's correct.

In order to not spam the main repo with updates, I plan on doing it once every two or three weeks, along with the book and nomicon repos.

I'm going to keep this ticket open as a "put this into the README", thanks!

@steveklabnik steveklabnik added the Enhancement Improvement in a non-prose section of the book label Apr 7, 2017
@steveklabnik steveklabnik changed the title How often is reference built and replaced on website? "How often is reference built and replaced on website?" should be in the README Apr 7, 2017
@mrhota
Copy link
Contributor Author

mrhota commented Apr 7, 2017

Can't we release the online, compiled docs separately from the release of nightly rust?

@steveklabnik
Copy link
Member

steveklabnik commented Apr 7, 2017

Sure, it's possible, but creating yet another duplicate URL for some docs seems like a bad tradeoff to me.

@Havvy
Copy link
Contributor

Havvy commented Sep 24, 2017

It might be best to document this process on the forge since this is cross-cutting and then put a link to that into the readme.

@steveklabnik
Copy link
Member

https://forge.rust-lang.org/release-process.html is now on the forge, but isn't exactly accessible.

@ehuss ehuss added the Meta Non-content issues (procedure, tooling, website, etc.) label Mar 11, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Enhancement Improvement in a non-prose section of the book Meta Non-content issues (procedure, tooling, website, etc.)
Projects
None yet
Development

No branches or pull requests

5 participants