Package: oca-core Version: 11.0.20180730-1 Severity: wishlist Dear Maintainer,
Odoo has several versions that are synchronized and maintain in the OCA community soft-fork called OCB (Odoo Community Backports), which is the source for this package. They are namely with a first major version plus minor version always being 0, so you have 10.0, 11.0, 12.0, 13.0..., being this last one the latest for now. Each year in October a new version arrives (14.0 will be next). There are patches on the last 3 active ones (now 13.0, 12.0 and 11.0), but no modification on main version. These versions can't be exchanged freely, as there's a data model associated with each version that is different from the others. The main value of OCB is double: A) Add non data model nor signature breaking changes that Odoo refuses by their reasons. B) Extend the support to out of official support versions(currently <=10.0), adding there patches that can be fixed in later versions. Then we need to manage all of these versions (or a reasonable number of them) as independent packages. What are the versions we should include? Latest 3 versions as Odoo? We are then losing value B). Only outdated versions? Then we lose value A). All of them? Maybe very costly. I'm open to extend information when needed and also to work on the final decision to be taken at this respect. -- System Information: Debian Release: bullseye/sid APT prefers focal-updates APT policy: (500, 'focal-updates'), (500, 'focal-security'), (500, 'focal'), (100, 'focal-backports') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.4.0-26-generic (SMP w/8 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8), LANGUAGE=es_ES.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
