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

[FIX] Upgrade maintainer-tools #44

Merged
merged 1 commit into from
Dec 11, 2020
Merged

[FIX] Upgrade maintainer-tools #44

merged 1 commit into from
Dec 11, 2020

Conversation

lmignon
Copy link
Contributor

@lmignon lmignon commented Dec 10, 2020

Includes fix for issue when installing docutils dependency.
docutils 0.15.1-post1 has installation issues with pip.
see pypa/pip#9203 (comment)

see https://travis-ci.com/github/OCA/wms/jobs/457408267#L297

Includes fix for issue when installing docutils dependency.
docutils 0.15.1-post1 has installation issues with pip.
see pypa/pip#9203 (comment)
@sbidoul sbidoul merged commit 7eaac76 into OCA:master Dec 11, 2020
@sbidoul sbidoul added this to the v1.1.0 milestone Dec 11, 2020
@lmignon lmignon deleted the patch-1 branch December 11, 2020 08:17
@sbidoul
Copy link
Member

sbidoul commented Dec 11, 2020

I have tagged v1.1.0. People who want to apply it can simply run copier -f update && pre-commit run -a. I'll deploy to all repos as soon as I can.
Note this release includes the move from travis to gha for the pre-commit step.

@yajo
Copy link
Member

yajo commented Dec 11, 2020

Do you think that it would be a good idea to add a workflow that, when doing a release, pushes it to all repos in supported branches (13.0 and 14.0 ATM)?

@sbidoul
Copy link
Member

sbidoul commented Dec 11, 2020

Sure an automation is needed, trust me it's not particularly fun to run it manually :). Making it robust is not entirely trivial. I'm polishing the script a little bit each time I run it. Unless something already cooked exists that I don't know?

@yajo
Copy link
Member

yajo commented Dec 11, 2020

Unless something already cooked exists that I don't know?

Nope, but I could draft it to let you put your script logic over it.

@dreispt
Copy link
Member

dreispt commented Dec 11, 2020

@sbidoul Thanks, if repo maintainers are informed, I think they can take this in their hands.

@yajo
Copy link
Member

yajo commented Dec 14, 2020

@dreispt IMHO automation is a better option.

Well... maintainers must be informed, for sure; but I think it'll be more comfortable to fix the few problems that might happen than to keep track of the template and do manual updates every now and then.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants