-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
10.0 fgarbely migration auditlog #705
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
10.0 fgarbely migration auditlog #705
Conversation
(cherry picked from commit 333d655)
(cherry picked from commit 4b8c8a1)
… (unit tests, ir.cron...) (cherry picked from commit 2b2c583)
…and HTTP requests models (cherry picked from commit 791489e)
(cherry picked from commit 872056c)
(cherry picked from commit a20cfbf)
…lete but slow) and Fast log (data input only, faster) (cherry picked from commit 043cf1b)
(cherry picked from commit 38ed67b)
(cherry picked from commit 5aaf6d6)
(cherry picked from commit 90ca923)
) * [IMP] index the columns we'll be searching for for every request * [FIX] singleton error if we saved the current session two times (cherry picked from commit c4ca262)
(cherry picked from commit 32adcba)
- Update documentation to point to the new auditlog menu locations. These were changed because the 8.0 version was referencing menus that do not exist in 9.0 - Change version from 8.0.X.Y.Z to 9.0.1.0.0 - Make the module installable again - Remove an unused parameter from pre-migration.py for versioning - Fix typos and remove commented out blocks of code that were irrelevant (cherry picked from commit a8dd839)
…is not required for version 9 (cherry picked from commit 60534d3)
(cherry picked from commit 479cecf)
…e' methods to the new API (cherry picked from commit 29e1860)
…e' methods to the new API (cherry picked from commit 29e1860)
|
FYI, you can follow this migration guide to avoid to cherry-pick manually each missing commit: https://github.com/OCA/maintainer-tools/wiki/Migration-to-version-10.0#technical-method-to-migrate-a-module-from-90-to-100-branch |
|
Thanks a lot. |
|
Hello @pedrobaeza I have seen that I forgot to change some things (according to the migration guide). Should I change this in a new commit, or should I close this PR and create a new one according to the migration guide? Thanks for your support. Regards, |
|
You can start from scratch on your local and follow the guide, and then cherry-pick the migration commit. Then, you just need to force push the result to the same branch name as the one of this PR ( |
|
New PR #707 Hello @pedrobaeza I was easier for me to create a completely new PR. |
Syncing from upstream OCA/server-tools (13.0)
First, I cherry picked all auditlog commits from branch 9.0, which was added after the creation of the branch 10.0.
Then, I made the changes in auditlog to make it work in v10.