Add the other dev phase dates to Status of Python versions

Aberta
#998 2 comentários 2 reações 1 responsável Ver no GitHub

@CAM-Gerlach já está trabalhando nisso.

Desde 6/12/2022.

Avaliação

Esta issue ainda não foi avaliada.

Descrição

infra topic-versions type-feature

As [discussed] on PR #988 and at the Python Docs Community meeting, the Status of Python versions table is missing an indication of the expected/actual cut-over point between bugfix and security-only releases, which is fairly important information in line with the other dates displayed there. This is standard for most pages like this, and the Wikipedia page has it.

Additionally, it would seem to be quite helpful, especially since this is the CPython developer guide, to also add the dates for the dev cycle start, alpha, beta and rc phases, to make it easier for devs to quickly check the current phase and when the next one starts.

We should, at least, add additional JSON fields with this information. Since unfortunately with Mermaid it doesn't seem possible to add multiple segments to the same line, and it would clutter the main chart and table to add all these dates, I suggest we output these dates to a separate chart and table in a "Development Status" section, leaving the main one at the top. Eventually, it would seem ideal to migrate the main chart and table (or at least a simplified version) to the main Python,org site, since it is focused on user-facing information, while the proposed new section would contain developer-facing information

#999 is a followup, adding the individual point release version dates as JSON and subsidiary tables. These could be added to the chart in the development status section (and perhaps the latest release added to one of the main tables), or possibly the more detailed charts could be added/moved to the per-version subsections.

Linguagem predominante
Python
Estrelas
2.1k
Forks
1k
Merge médio
2d 12h
PRs com merge (30d)
12

Guia de contribuição

Abrir o guia de contribuição

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de python/devguide

Todas as issues de python/devguide

Issues semelhantes

Mais issues de Python

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.