Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

To-do list for release 2.12.0 #5250

Closed
9 tasks done
Pierre-Sassoulas opened this issue Nov 3, 2021 · 2 comments 路 Fixed by #5302
Closed
9 tasks done

To-do list for release 2.12.0 #5250

Pierre-Sassoulas opened this issue Nov 3, 2021 · 2 comments 路 Fixed by #5302
Assignees
Labels
Maintenance Discussion or action around maintaining pylint or the dev workflow
Milestone

Comments

@Pierre-Sassoulas
Copy link
Member

Pierre-Sassoulas commented Nov 3, 2021

Might as well create an issue from the unofficial todo list (hidden in dozen of comment 馃槃)

Originally posted by @Pierre-Sassoulas in pylint-dev/astroid#1217 (comment)

TODO for 2.12.0 (the last python > 3.6.0 release):

@Pierre-Sassoulas Pierre-Sassoulas added Blocker 馃檯 Blocks the next release Maintenance Discussion or action around maintaining pylint or the dev workflow labels Nov 3, 2021
@Pierre-Sassoulas Pierre-Sassoulas added this to the 2.12.0 milestone Nov 3, 2021
@Pierre-Sassoulas Pierre-Sassoulas self-assigned this Nov 13, 2021
Pierre-Sassoulas added a commit that referenced this issue Nov 14, 2021
Pierre-Sassoulas added a commit that referenced this issue Nov 14, 2021
Pierre-Sassoulas added a commit that referenced this issue Nov 14, 2021
@DanielNoord
Copy link
Collaborator

@Pierre-Sassoulas Do you still want to auto update all expected outputs of the functional tests, to decrease future diffs? Might be good to add it to the todo list if you do.

@cdce8p
Copy link
Member

cdce8p commented Nov 19, 2021

Do you still want to auto update all expected outputs of the functional tests, to decrease future diffs? Might be good to add it to the todo list if you do.

I though it might make sense to do that together with #5336. We should update all message outputs for that anyway.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Maintenance Discussion or action around maintaining pylint or the dev workflow
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants