Migration to version 18.0

Open
  • Is something wrong?
#499 8 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

@kwoychesko is already working on this.

Since May 26, 2026.

  • #615 by @kwoychesko — open

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
backend

Research direction

Read the OCA migration guide linked in the issue, then inspect the repository’s document_page module and its migration checklist conventions. Migrate document_page to version 18.0 and submit the module migration; the issue does not specify particular files or tests, so use the guide to identify the required changes and validation.

Written by the indexing model from the issue text.

Description

help wanted no stale work in progress

Todo

https://github.com/OCA/maintainer-tools/wiki/Migration-to-version-18.0

Modules to migrate

  • attachment_zipped_download - By @victoralmau - #520
  • document_knowledge - By @Kimkhoi3010 - #503
  • document_page
  • document_page_access_group - By @BhaveshHeliconia - #523
  • document_page_access_group_user_role - By @Anushapadinharepurakkal - #543
  • document_page_approval - By @HeliconiaSolutions - #524
  • document_page_group - By @BhaveshHeliconia - #525
  • document_page_partner - By @Anushapadinharepurakkal - #540
  • document_page_portal - By @kwoychesko - #615
  • document_page_product - By @victoralmau - #606
  • document_page_reference - By @Anushapadinharepurakkal - #550
  • document_page_tag - By @BhaveshHeliconia - #527
  • document_url - By @BhaveshHeliconia - #542

Missing module? Check https://github.com/OCA/maintainer-tools/wiki/%5BFAQ%5D-Missing-modules-in-migration-issue-list

Dominant language
HTML
Stars
256
Forks
405
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from OCA/knowledge

All issues in OCA/knowledge

Similar issues

More Backend & API Design issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.