rework docs for 0.11.0 release

[mattip]

• Replace 0.11 docs with the correct 0.11. ones (note the '.'
• Replace the main ... text in the version and title (what you see when you hover on the tab) with 0.11.0

Related to issue #4574

[facebook-github-bot]

💊 CI failures summary and remediations

As of commit 3f7f495 (more details on the Dr. CI page):

---

Commit 3f7f495 was recently pushed. Waiting for builds...

---

This comment was automatically generated by Dr. CI (expand for details).

Follow this link to opt-out of these comments for your Pull Requests.

Please report bugs/suggestions to the (internal) Dr. CI Users group.

Click here to manually regenerate this comment.

[mattip]

@brianjo

[NicolasHug]

Thanks for the PR @mattip , just a question below

Related to issue #4574

I think you meant #4754 :)

[NicolasHug]

Are these types of changes intended? Looks like this file comes from the main branch, so it would be OK to leave main here?

[mattip]

They are the 0.11.0 release documents. The nightly builds (unstable) should be called main. Also when 0.12 is released, these documents will not change.

[mattip]

This should all have been part of the build that occurred when the release was tagged, I am not sure why I had to manually correct it.

[NicolasHug]

Sorry I'm not sure I understand.

Where can I see the unstable in this PR? I'm only seeing this:

Also in the main folder I'm seing this:

but it's confusing to see "Torchvision 0.11.0 documentation" when hovering over the tab. Are these intended?

[brianjo]

@mattip I think that some of the edits in your PR might be in the main folder by mistake. (main is our nightly generated docs) I think you meant for your version edits to happen only in the 0.11 folder. Is that correct?

[mattip]

Ahh, whoops, sorry. I will fix that.

[NicolasHug]

Thanks @mattip , LGTM. Is it safe to merge despite the apparent CI build issues?

[mattip]

Is it safe to merge despite the apparent CI build issues?

I don;t think CI is actually turned on for this branch, there is no config file.
I did check a few things locally, but this is a big change. You may want to download it and look how the html renders in your browser: whether the version selector does what it should.

[vadimkantorov]

Also, pls fix the not working links to the code pytorch/pytorch#67237

[NicolasHug]

whether the version selector does what it should

Are you talking about this?

It automatically redirects me to https://pytorch.org/vision/versions.html

[mattip]

Are you talking about this?

Huh? That should not be showing main (0.12.0a0+9e3fecd), it should be showing 0.11.0 in this PR. Then when you click on it, the versions.html should come up, and link to 0.11 (without the '.').

Also, pls fix the not working links to the code pytorch/pytorch#67237

I think that is a different issue, this PR is about getting the proper 0.11.0 docs into place.

[NicolasHug]

That should not be showing main (0.12.0a0+9e3fecd), it should be showing 0.11.0 in this PR.

I do see 0.11.0 when looking at file:///Users/nicolashug/dev/vision/0.11/index.html

Then when you click on it, the versions.html should come up, and link to 0.11 (without the '.').

Clicking on it always redirects to https://pytorch.org/vision/versions.html: there's no 0.11 nor 0.11.

[mattip]

Clicking on it always redirects to https://pytorch.org/vision/versions.html: there's no 0.11 nor 0.11.

Cool. When you follow that link, it shows a page with 0.11.0 which points to https://pytorch.org/vision/0.11/, so that is all good.

I removed the mistakenly modified "main/*" files.

[NicolasHug]

Thank you Matti, this makes sense now. Chatting with @brianjo also helped clarify a few things.

This LGTM, it's the WE soon so I'll merge on Monday just to be extra careful :)