itsulu/itsulu-blog-publisher
2
0
Fork 0
mirror of https://gitlab.com/itsulu-odoo/itsulu-blog-publisher.git synced 2026-05-30 23:41:23 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions
itsulu-blog-publisher/PORTING.md
Nicholas Riegel 6702c8390e release: v0.5.0 — establish Odoo 19.0 branch (multi-version support) 
Seed the 19.0 series branch from the 17.0 baseline and wire up the
per-Odoo-version structure:
- .odoo-series = 19.0; Dockerfile FROM odoo:19.0; manifest 19.0.0.5.0
- PORTING.md tracks the Odoo-19 API porting checklist
- README retargeted to 19.0 with a porting-in-progress notice
- CHANGELOG v0.5.0 entry

NOTE: code is seeded from 17.0 — the Odoo-19 port is NOT yet verified
(see PORTING.md). Not deploy-ready on a 19.0 instance until the suite
runs green there.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-05-30 11:15:50 -04:00

1.6 KiB
Raw Permalink Blame History

Porting status — Odoo 19.0 branch

This branch targets Odoo Community 19.0. It was seeded from the 17.0 baseline (the main line) and the Odoo-19-specific porting is tracked here. Until every item below is verified, treat this branch as work in progress — do not deploy to a 19.0 instance expecting it to work unverified.

The product feature set is the same across all Odoo branches; only the Odoo-API-specific code differs. See CLAUDE.md §15 for the branch model and §11.5 / §12 for known version-specific gotchas.

Series markers (done)

  • .odoo-series = 19.0
  • Dockerfile base image = odoo:19.0
  • manifest version prefix = 19.0. (via bump-version.sh)

API porting checklist (verify on a real Odoo 19.0 instance)

  • Module installs cleanly: odoo -i itsulu_blog_publisher on 19.0
  • blog.post body field name (was content in 17.0 — confirm for 19.0)
  • mail.template rendering (subject inline_template, body qweb type="html")
  • mail.template._render_field signature/return shape
  • website_blog dependency + view inheritance still valid
  • Wizard / settings views pass RELAXNG validation on 19.0
  • ir.cron data format
  • Python version compatibility (19.0 ships on a newer Python)
  • Full test suite green on a 19.0 template DB (K8s job, §8)

How to work this branch

  1. Stand up a 19.0 template DB (mirror §8, base image odoo:19.0).
  2. Run the suite, fix failures one Odoo-API difference at a time.
  3. Record each gotcha in CLAUDE.md §12 tagged with the series.
  4. When green, cut a release on this branch (bump-version.sh → tag 19.0-vX.Y.Z).