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’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Change version for 2.7.3 release, modify release process #4261

Merged

Conversation

Pierre-Sassoulas
Copy link
Member

Description

We wanted to avoid introducing new problems by separating feature and bug fix in 2.7.x. Right now we have 4/5 rebase conflicts to handle in order to do that. I'd argue more problem will happen because of 5 conflict resolution than with 3 new features.

Type of Changes

Type
📜 Docs

@Pierre-Sassoulas Pierre-Sassoulas added this to the 2.7.3 milestone Mar 29, 2021
@coveralls
Copy link

Coverage Status

Coverage decreased (-0.008%) to 91.446% when pulling 8398c7f on Pierre-Sassoulas:prepare-for-2.7.3 into a37c643 on PyCQA:master.

@Pierre-Sassoulas Pierre-Sassoulas merged commit 13dae7c into pylint-dev:master Mar 29, 2021
@Pierre-Sassoulas Pierre-Sassoulas deleted the prepare-for-2.7.3 branch March 29, 2021 19:00
@Pierre-Sassoulas Pierre-Sassoulas added Maintenance Discussion or action around maintaining pylint or the dev workflow and removed task labels Jun 23, 2022
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 this pull request may close these issues.

None yet

2 participants