# 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)

- [x] `.odoo-series` = `19.0`
- [x] `Dockerfile` base image = `odoo:19.0`
- [x] 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`).