Beta FAQ update #3346
Beta FAQ update #3346
Conversation
| @@ -45,7 +45,8 @@ Here are some tips. | |||
| * JSON API: ``https://pypi.org/pypi/{name}/json`` returns the | |||
| expected JSON response directly. See :doc:`json`. | |||
|
|
|||
| * XML-RPC API: see :ref:`changes-to-legacy-api`. | |||
| * XML-RPC API: see :ref:`changes-to-legacy-api`. Will be deprecated in | |||
| the future; switch to the RSS or JSON APIs. | |||
There was a problem hiding this comment.
Should we call to action to file issues for things that they use that only exists in the XMLRPC API?
There was a problem hiding this comment.
Good call! Fixed.
warehouse/templates/pages/help.html
Outdated
| </ul> | ||
| <p> | ||
| While we are in pre-production, our infrastructure cannot yet support all of the traffic generated by our users running <code>pip install</code>. We therefore ask that you do not use this version of PyPI for production codebases. | ||
| While we are in beta, the pypi.org infrastructure cannot yet support all of the API traffic generated by our users running <code>pip install</code>, so don't explicitly point to it in your production setups. But we're occasionally redirecting portions of that traffic in load tests we announce <a href="http://status.python.org/">on our status page</a>. |
There was a problem hiding this comment.
I think we can say we're generally ready for traffic? Or will be once @ewdurbin gets the XMLRPC caching sorted out? Are we ready to tell people they can start shifting their own traffic to Warehouse now? I'm not sure how to word it really, but like "Early Adopter" traffic is probably not going to knock us over?
There was a problem hiding this comment.
I'd like to encourage early adopter traffic, and can find a way to word it if @ewdurbin says it's ok.
There was a problem hiding this comment.
Once we get #3336 cleared up, we'll be all set to start calling it beta. Right now it's just too costly if a user with lots of projects logs in.
There was a problem hiding this comment.
@ewdurbin Good info, thanks. So, once we're in beta, what level of traffic are you ok with encouraging? (this is kind of "what does 'beta' mean to you?")
There was a problem hiding this comment.
Anything that arrives organically is probably fine. We may be migrating our backend database as well now... so perhaps we should wait until after that?
brainwane
force-pushed
the
beta-faq
branch
2 times, most recently
from
f45a4b7 to
9a90be3
Compare
|
Ready for re-review with new traffic wording. |
brainwane
force-pushed
the
beta-faq
branch
3 times, most recently
from
747b51c to
082588d
Compare
Marking as
blockedsince I know this depends on updating the banner inpypi-theme. I suggest#betaandbeta()for thehelp/section label, which would require the banner changing its link.@ewdurbin @dstufft @nlhkabu @di I am a thousand percent open to critique on this FAQ change; what promises should we be making about infra & features? What should we encourage people to do or avoid?
Ref. #2518. (does not close entirely; we'll close it after we launch/redirect)