Skip to content

Conversation

@BT-fgarbely
Copy link

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.

sebalix and others added 19 commits January 18, 2017 15:55
… (unit tests, ir.cron...)

(cherry picked from commit 2b2c583)
…and HTTP requests models

(cherry picked from commit 791489e)
(cherry picked from commit 872056c)
…lete but slow) and Fast log (data input only, faster)

(cherry picked from commit 043cf1b)
)

* [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)
- 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)
@pedrobaeza pedrobaeza mentioned this pull request Jan 19, 2017
63 tasks
@pedrobaeza
Copy link
Member

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

@BT-fgarbely
Copy link
Author

Thanks a lot.
I didn't know this checklist.

@BT-fgarbely
Copy link
Author

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,

@pedrobaeza
Copy link
Member

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 (10.0_fgarbely_migration_auditlog), and this PR can be recycled for the new code.

@pedrobaeza pedrobaeza closed this Jan 20, 2017
@BT-fgarbely
Copy link
Author

New PR #707

Hello @pedrobaeza

I was easier for me to create a completely new PR.

SiesslPhillip pushed a commit to grueneerde/OCA-server-tools that referenced this pull request Nov 20, 2024
Syncing from upstream OCA/server-tools (13.0)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants