l10n_din5008_move_salesperson
in l10n-germany · source on GitHub
Add sales person of the move in DIN 5008 Invoice report
Category: Account · NICO-SOLUTIONS · LGPL-3
| Series | Status | Details | Code |
|---|---|---|---|
| 16.0 | —Not tested | no branch | |
| 17.0 | —Not tested | no branch | |
| 18.0 | —Not tested | no branch | |
| 19.0 | ✓Installs | · run 2026-09-06 · 19.0.1.0.0 | on GitHub |
| 20.0 | —Not tested | no branch |
Odoo 20.0 dev — development line
A different statement from the table above. There: the module as published, on a released platform. Here: the module’s code with its manifest version mechanically raised, on a platform that has not been released and changes daily.
| Status | Details |
|---|---|
| ✓runs | · version 19.0.1.0.0 → 19.5.1.0.0, code unchanged · run 2026-09-10 · odoo 19.5 · modidx/odoo:master-deps-20260910 |
Provenance: __manifest__.py sha256 a39786e43b38e8e7… · tree of 11 files without the manifest, sha256 4c6ae4dc9d58ca85…
This does not say the module is compatible with Odoo 20.0, and does not say it installs on Odoo 20.0 — on a stock platform it will not, until its maintainer raises the version. Why we raise the version
Odoo 20.0 — the branch itself
The same frozen code, run again against the real 20.0 branch. The run above used Odoo’s development line before the branch was cut; this one used the branch, pinned to one commit.
| Status | Details |
|---|---|
| ✓runs | · version 19.0.1.0.0 → 20.0.1.0.0, code unchanged · run 2026-09-18 · odoo 20.0 · modidx/odoo:20.0-deps-20260918 |
Provenance: __manifest__.py sha256 a39786e43b38e8e7… · tree of 11 files without the manifest, sha256 4c6ae4dc9d58ca85…
This does not say the module is compatible with Odoo 20.0, and does not say it installs on Odoo 20.0 — on a stock platform it will not, until its maintainer raises the version. Why we raise the version
Depends on
| Module | Status | Checked |
|---|---|---|
| l10n_din5008 | core | ships with Odoo |
Result looks wrong? Tell us — we will show the log or run it again. Report a wrong result