Discussion : Change to the release process

.github/dependabot.yml

@@ -3,7 +3,7 @@ updates:
   - package-ecosystem: "pip"
     directory: "/"
     schedule:
-      interval: "daily"
+      interval: "weekly"
     labels:
       - "dependency"
     open-pull-requests-limit: 10

ChangeLog

@@ -2,12 +2,12 @@
 Pylint's ChangeLog
 ------------------
 
+..
+  Put new features and bugfixes here and also in 'doc/whatsnew/2.8.rst'
+
 What's New in Pylint 2.8.0?
 ===========================
-Release date: Undefined
-
-..
-  Put new features here and also in 'doc/whatsnew/2.8.rst'
+Release date: 2021-04-25
 
 * New refactoring message ``consider-using-with``. This message is emitted if resource-allocating functions or methods of the
   standard library (like ``open()`` or ``threading.Lock.acquire()``) that can be used as a context manager are called without
@@ -34,9 +34,13 @@ Release date: Undefined
   ``typing.Final``
 
 * The packaging is now done via setuptools exclusively. ``doc``, ``tests``, ``man``, ``elisp`` and ``Changelog`` are
-  not packaged anymore - reducing the size of the package by 75%. Debian packaging is now  (officially) done in
-  https://salsa.debian.org/python-team/packages/pylint. The 'doc' extra-require has been removed. ``__pkginfo__`` now
-  only contain ``__version__`` (also accessible with ``pylint.__version__``), other meta-information are still
+  not packaged anymore - reducing the size of the package by 75%.
+
+* Debian packaging is now  (officially) done in https://salsa.debian.org/python-team/packages/pylint.
+
+* The 'doc' extra-require has been removed.
+
+* ``__pkginfo__`` now only contain ``__version__`` (also accessible with ``pylint.__version__``), other meta-information are still
   accessible with ``import importlib;metadata.metadata('pylint')``.
 
 * COPYING has been renamed to LICENSE for standardization.
@@ -62,14 +66,6 @@ Release date: Undefined
   (For example, 'typing.Dict' can be replaced by 'dict', and 'typing.Unions' by '|', etc.)
   Make sure to check the config options if you plan on using it!
 
-
-What's New in Pylint 2.7.5?
-===========================
-Release date: Undefined
-
-..
-  Put bug fixes that will be cherry-picked to latest major version here
-
 * Reactivates old counts in report mode.
 
   Closes #3819

doc/development_guide/contribute.rst

@@ -33,7 +33,7 @@ astroid:
 Discord server
 --------------
 
-https://discord.gg/kFebW799
+https://discord.gg/Egy6P8AMB5
 
 Mailing lists
 -------------

doc/release.md

@@ -46,18 +46,11 @@ twine upload dist/*
 
 ## Post release
 
-### New branch to create for major releases
+### Merge tags in master for pre-commit
 
-The master branch will have all the new features for the `X.Y+1` version
-
-If you're doing a major release, you need to create the `X.Y` branch where we will
-cherry-pick bugs to release the `X.Y.Z+1` minor versions
-
-### Merge tags in master for minor releases
-
-Merge the tag `X.Y.Z` in the main branch by doing a history only merge. It's done in
-order to signal that this is an official release tag, and for `pre-commit autoupdate` to
-works.
+If the tag you just made is not part of the main branch, merge the tag `X.Y.Z` in the
+main branch by doing a history only merge. It's done in order to signal that this is an
+official release tag, and for `pre-commit autoupdate` to works.
 
 ```bash
 git checkout master
@@ -74,8 +67,8 @@ issue labelled as blocker.
 
 #### Changelog
 
-- 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
+- Create a new section, with the name of the release `X.Y.Z+1` or `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`.
@@ -87,6 +80,5 @@ at the examples from `doc/whatsnew`.
 
 ### Versions
 
-Update `__version__` to `X.Y+1.0` in `pylint/__pkginfo__.py` for `master` and to
-`X.Y.Z+1` for the `X.Y` branch. `dev_version` should also be back to an integer after
-the tag.
+Update `__version__` to `X.Y+1.0` or `X.Y.Z+1` in `__pkginfo__`. `dev_version` should
+also be back to an integer after the tag.

setup.cfg

@@ -31,13 +31,12 @@ classifiers =
     Topic :: Software Development :: Testing
 keywords = static code analysis linter python lint
 project_urls =
-    "What's New" = https://pylint.pycqa.org/en/latest/whatsnew/
-    "Bug tracker" = https://github.com/PyCQA/pylint/issues
-    "Discord server" = https://discord.gg/kFebW799
-    "User manual" = http://pylint.pycqa.org/en/latest/
-    "Contributing" = http://pylint.pycqa.org/en/latest/development_guide/contribute.html
-    "Technical references" = http://pylint.pycqa.org/en/latest/technical_reference/index.html
-    "Mailing list" = mailto:code-quality@python.org
+    What's New = https://pylint.pycqa.org/en/latest/whatsnew/
+    Bug tracker = https://github.com/PyCQA/pylint/issues
+    Discord server = https://discord.gg/Egy6P8AMB5
+    User manual = http://pylint.pycqa.org/en/latest/
+    Contributing = http://pylint.pycqa.org/en/latest/development_guide/contribute.html
+    Technical references = http://pylint.pycqa.org/en/latest/technical_reference/index.html
 
 [options]
 packages = find: