To-do list for release 2.13.0

[Pierre-Sassoulas]

• Remove the check_docs extension and remove any references to it #5730
• Refactor the Confidence to be more accurate of what it means see Fix a crash on psycopg2 for elif used  #5369 (comment) Done in Modify the description of HIGH confidence in pylint.interfaces #5519
• Release astroid 2.10 and upgrade the version in pylint (Fixes to tests due to (possible) new tolineno behaviour #5802)
• 1 issue which needs some further investigation: [2.12.x] false positives: no-name-in-module, import-error #5645,
• 1 issue which just need an implementation: Add proper tests for the change to the module loader in astroid #5341
• 1 project maintenance issue: Document a better release process than the current one #4701
• 1 project maintenance issue: Simplify hard to maintain copyright notice  #5877
• Another project maintenance issue: Pylint needs to forbid to re-use the msgid or symbol of old deleted msgid/symbol #5729
• A lot of issues depending on astroid 2.10.

[DanielNoord]

Shall we start the discussion on check_docs? The change that deprecated check_docs for backward compatibility is 6 years old, see 9423e31

Maintaining it is problematic as we can't load the same plugin twice without crashing on the option registering. The change to use docparams is also quite easy (just change check_docs to docparams in your rcfile).

I would vote in favour of removing.

[Pierre-Sassoulas]

I would vote in favor of removing.

Same here, I think it's pretty safe to do at this point.

[DanielNoord]

I'm thinking about moving this to 2.14 because of the amount of work involved and the number of duplicate issues we must handle that are already fixed in main and could be released :)

Originally posted by @Pierre-Sassoulas in #5466 (comment)

Just my two cents about 2.13:
Looking at open issues and PRs for 2.13:

1. There are 4 PRs which are in final stages of review and should be mergeable if we all get together and review and iterate on them
2. 1 issues which needs some further investigation: [2.12.x] false positives: no-name-in-module, import-error #5645,
3. 1 issues which just need an implementation: Add proper tests for the change to the module loader in astroid #5341
4. 2 project maintenance issues: Document a better release process than the current one #4701, Pylint needs to forbid to re-use the msgid or symbol of old deleted msgid/symbol #5729
5. A lot of issues depending on astroid 2.10.

From pylint's side that's actually quite manageable, although these are all issues that are less likely to attract contributors due to their difficulty.
If anything focus should probably be on astroid 2.10 and trying to clear or move some of the backlog there. There are 6 opens PRs, one of which is a crash, that depend on it.

Edit: Updated the to-do to reflect current state.

[Pierre-Sassoulas]

If anything focus should probably be on astroid 2.10

👍

[michael-k]

If anything focus should probably be on astroid 2.10

Now that this has been resolved in #5802, is there anything blocking a 2.13 release?

[Pierre-Sassoulas]

No, we "only" need to handle the list of remaining issues in the milestone.