Manuel Kaufmann

I think we shouldn't do this work at this point considering that we are deploying `app.` today. We probably just can make the switch and make `app.` official after a...

We talked about not doing this issue and try to move more users to the new dashboard by doing other small tasks.

> Pass the object that we already have from using the unresolver / doc serving views What's the object you mean here? The `Project` itself? If that's what you are...

I just want to note here that I found myself (while working on #11205) wanting to share the `Resolver()` instance all across the request. This is because checking the canonical...

"Stale" is not a state itself. It's basically a build in `triggered` state that has been in that state for more than 5 minutes: https://github.com/readthedocs/readthedocs.org/blob/0b09fda4be8a2e955fe7041324217a3f6ed42b15/readthedocs/builds/models.py#L951-L954 You should probably move that...

Yeah. I'm saying that we should remove this logic from the backend and put it in the frontend because it's not used in the backend and you are having issue...

If the fontend is using the API to fetch all the `Build` data and display it there, I'd say we should move this two-lines logic to the frontend and remove...

It would be good to move forward with this PR. I also found myself wanting to write `test` and list all the versions that start with `test` instead of _only...

@agjohnson yes, you are right. The problem I'm having is that there is always a version selected while you are typing. So, there is no way to select "all the...

@ericholscher that was the initial work, yeah. However, we need to explain `$READTHEDOCS_OUTPUT` variable and create all the examples I mentioned in the description into `test-builds` and show them in...