diff options
| author | Pierre Sassoulas <pierre.sassoulas@gmail.com> | 2021-02-21 15:33:25 +0100 |
|---|---|---|
| committer | Pierre Sassoulas <pierre.sassoulas@gmail.com> | 2021-02-21 19:19:49 +0100 |
| commit | da2473da20ad03731b8a05b23b5a34a48cf5fb91 (patch) | |
| tree | 66bb68a2efb6afad297537cdfa5698542ed548e1 /doc/release.md | |
| parent | 77ed8cdfc1a1956d0bbd4c38cf2a228de87b88b7 (diff) | |
| download | pylint-git-da2473da20ad03731b8a05b23b5a34a48cf5fb91.tar.gz | |
Add 2.8.0 in the Changelog
Diffstat (limited to 'doc/release.md')
| -rw-r--r-- | doc/release.md | 9 |
1 files changed, 6 insertions, 3 deletions
diff --git a/doc/release.md b/doc/release.md index fe9d0e7b8..a793a646a 100644 --- a/doc/release.md +++ b/doc/release.md @@ -58,13 +58,16 @@ if it's an issue labelled as blocker. ### Files to update after releases #### Changelog -Create a new section, with the name of the release ``X.Y.Z+1`` (or ``X.Y+1.0`` for -major release) and the estimated date when it is going to be published. If + +* Create a new section, with the name of the release ``X.Y.Z+1`` on the ``X.Y`` branch. +* If it's a major release, also create a new section for ``X.Y+1.0`` on the master branch + +You need to add the estimated date when it is going to be published. If no date can be known at that time, we should use ``Undefined``. #### Whatsnew -Only for major release, create a new ``What's new in Pylint X.Y+1`` document +If it's a major release, create a new ``What's new in Pylint X.Y+1`` document Take a look at the examples from ``doc/whatsnew``. ### Versions |