On Aug 12, 2021, at 12:58, Jack DeVries wrote:
> > If you look at the version picker on docs.python.org you will see that we
> > already have the docs for 3.10 and 3.11 available. I don't know if they are
> > updated per release right now or per commit.
>
> I understand that they are available
> If you look at the version picker on docs.python.org you will see that we
already have the docs for 3.10 and 3.11 available. I don't know if they are
updated per release right now or per commit.
I understand that they are available options. To clarify my suggestion, I
think that 3.11 should be
On Thu, Aug 12, 2021 at 6:04 AM Jack DeVries wrote:
> On a broader note, how does the deployment pipeline for documentation
> work? It seems to me that for branches that are in pre-release (3.10) or
> active development (3.11), the documentation should be continuously
> deployed, while
On a broader note, how does the deployment pipeline for documentation work?
It seems to me that for branches that are in pre-release (3.10) or active
development (3.11), the documentation should be continuously deployed,
while deployment of changes to earlier documentation should follow minor
11.08.21 21:35, Brett Cannon пише:
> So my question is whether we want to push to be more diligent about
> updating What's New by b1 so people can provide feedback during the
> betas beyond just reporting breaking changes?
I think that What's New should be updated as soon as possible,
immediately
Yes, I think we should get it done by b1. For some reason it never
occurred to me to add this to What's New. Someone just reported this on
bpo this week. I'll try and get a PR together this week.
Eric (who doesn't feel picked on!)
On 8/11/2021 2:35 PM, Brett Cannon wrote:
Not to specifically
