Split up the Changelog
@AA-Turner arbeitet bereits daran.
Seit 15.8.2025.
- Vorherrschende Sprache
- Python
- Sterne
- 77.2k
- Forks
- 35.9k
- PR-Merge-Kennzahlen
- PR-Kennzahlen ausstehend
Beschreibung
Documentation
Originally proposed in https://github.com/python/docs-community/issues/98
The full changelog is rather long, containing every NEWS entry since Python 3.5. We propose splitting it up into smaller individual files.
Doing this will also improve (parallel) builds -- build/NEWS (the file included by changelog.rst) is currently c. 55,000 lines long, the next longest file is 'only' 6,000 lines.
Consensus on the docs-community issue seemed to align with my proposal of splitting the changelog by minor version, meaning that we would have e.g. whatsnew/changelog/3.6.html.
I suggest that whatsnew/changelog/index.html would contain the entries for a pre-beta version (e.g. currently the 3.15 pre-alphas), but we could put these straight into whatsnew/changelog/3.15.html. Any strong opinions?
If we are happy to do this, I will propose the needed changes to blurb & then open PRs in CPython.
A
Beitragsleitfaden
Erste Schritte
- Lies das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreib ins Issue, dass du es übernimmst — das erspart doppelte Arbeit.
- Forke das Repository und arbeite in einem Branch.
- Öffne einen Pull Request, der die Issue-Nummer nennt.
Bewertung
Dieses Issue wurde noch nicht bewertet.