-
-
Notifications
You must be signed in to change notification settings - Fork 341
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
[17.0][MIG] document_knowledge: Migration to 17.0 #447
Conversation
* Copyright and various stuff * Contributors * External ID not found in the system: base.group_document_user
Currently translated at 93.9% (31 of 33 strings) Translation: knowledge-11.0/knowledge-11.0-knowledge Translate-URL: https://translation.odoo-community.org/projects/knowledge-11-0/knowledge-11-0-knowledge/pt_BR/
It solves this: OCA#179
Updated by Update PO files to match POT (msgmerge) hook in Weblate.
Otherwise the module grants too wide permissions for all users.
Updated by "Update PO files to match POT (msgmerge)" hook in Weblate. Translation: knowledge-12.0/knowledge-12.0-knowledge Translate-URL: https://translation.odoo-community.org/projects/knowledge-12-0/knowledge-12-0-knowledge/
Currently translated at 57.7% (15 of 26 strings) Translation: knowledge-12.0/knowledge-12.0-knowledge Translate-URL: https://translation.odoo-community.org/projects/knowledge-12-0/knowledge-12-0-knowledge/fr/
This PR has the |
@m1k3lm please split pre-commit commit from the migration itself, and also squash latest administrative commits into the generating one. |
In v16 Odoo has its own knowledge module
04d31be
to
959d9bc
Compare
@pedrobaeza not sure If I got what you meant, let see if it is ok like this. |
There's still no 2 commits, one for pre-commit stuff, and another for the migration itself. See https://github.com/OCA/maintainer-tools/wiki/Migration-to-version-17.0#technical-method-to-migrate-a-module-from-160-to-170-branch for the original method to follow. |
Sorry, @pedrobaeza I still don't understand what you mean. 959d9bc is the migration itself all the previous ones are what you call "pre-commit stuff"? If I sqash all of them into one the commit history would get lost. |
You didn't follow the migration procedure, splitting the stuff resulting of running |
959d9bc
to
7bb2333
Compare
Now the commits are mostly correct (the version shouldn't be changed in the pre-commit commit), but you should also switch the configuration view ( |
7bb2333
to
78aa3fe
Compare
78aa3fe
to
3484421
Compare
I did not change anything in the pre-commit, just run Thanks a lot for your time @pedrobaeza |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the efforts:
/ocabot merge nobump
On my way to merge this fine PR! |
@pedrobaeza can you send to merge again? Don´t know why but oca bot didn't merge it |
System glitches... /ocabot merge nobump |
This PR looks fantastic, let's merge it! |
Congratulations, your PR was merged at 07d98d3. Thanks a lot for contributing to OCA. ❤️ |
/ocabot migration document_knowledge