Migration to version 19.0

[hbrunn]

I'm starting to work on initializing the 19.0 branch this week, with the usual openupgrade_framework and base migration script.

• account_payment - By @hbrunn - [19.0][MIG] account_payment #5527
• analytic - By @hbrunn - [19.0][MIG] account #5509
• auth_signup - By @hbrunn - [19.0][MIG] portal #5501
• base - By @hbrunn - [19.0][MIG] base #5446
• base_setup - By @hbrunn - [19.0][MIG] mail+dependencies #5466
• calendar - By @MiquelRForgeFlow - [19.0][MIG] calendar #5613
• digest - By @hbrunn - [19.0][MIG] digest #5505
• don't warn about changes in the base module in the analysis cronjob if only the general log file is changed (done in [18.0][IMP] analysis cronjob v19 + improvements #5389)
• google_recaptcha - By @MiquelRForgeFlow - [19.0][MIG] website dependencies #5580
• have the test databases created and updated by a cronjob (done in [18.0][IMP] add a github workflow that generates test databases used in CI #5375)
• hr - By @hbrunn - [19.0][MIG] hr+dependencies #5566
• hr_expense - By @hbrunn - [19.0][MIG] hr_expense #5587
• hr_holidays - By @hbrunn - [19.0][MIG] hr_holidays #5598
• hr_recruitment - By @hbrunn - [19.0][MIG] hr_recruitment #5612
• html_editor - By @hbrunn - [19.0][MIG] mail+dependencies #5466
• l10n_be - By @mihien - [19.0][MIG] l10n_be #5561
• mrp - By @hbrunn - [19.0][MIG] mrp #5558
• mrp_account - By @hbrunn - [19.0][MIG] mrp #5558
• onboarding - By @hbrunn - [19.0][MIG] account #5509
• payment - By @hbrunn - [19.0][MIG] payment #5526
• phone_validation - By @hbrunn - [19.0][MIG] hr+dependencies #5566
• point_of_sale - By @hbrunn - [19.0][MIG] point_of_sale #5565
• portal - By @hbrunn - [19.0][MIG] portal #5501
• pos_discount - By @hbrunn - [19.0][MIG] point_of_sale #5565
• pos_hr - By @hbrunn - [19.0][MIG] point_of_sale #5565
• product - By @hbrunn - [19.0][MIG] product #5477
• project - By @hbrunn - [19.0][MIG] project + dependencies #5572
• purchase - By @hbrunn - [19.0][MIG] purchase #5559
• purchase_stock - By @hbrunn - [19.0][MIG] purchase #5559
• rating - By @hbrunn - [19.0][MIG] project + dependencies #5572
• resource - By @hbrunn - [19.0][MIG] resource #5504
• sale - By @hbrunn - [19.0][MIG] sale #5529
• sale_management - By @hbrunn - [19.0][MIG] sale_management #5531
• sale_purchase - By @hbrunn - [19.0][MIG] sale_purchase, sale_purchase_stock (nothing to do) #5560
• sale_stock - By @hbrunn - [19.0][MIG] sale_stock #5555
• sales_team - By @hbrunn - [19.0][MIG] sales_team #5528
• social_media - By @MiquelRForgeFlow - [19.0][MIG] website dependencies #5580
• spreadsheet_dashboard - By @eduezerouali-tecnativa - [19.0][MIG] spreadsheet_dashboard #5606
• stock - By @hbrunn - [19.0][MIG] stock, stock_account #5547
• stock_account - By @hbrunn - [19.0][MIG] stock, stock_account #5547
• uom - By @hbrunn - [19.0][MIG] uom #5472
• utm - By @MiquelRForgeFlow - [19.0][MIG] website dependencies #5580
• v19 adaptions to openupgradelib: [IMP] load_data: support v19 upgrade_path openupgradelib#427
• openupgrade_framework - By @hbrunn - [19.0] initialize+openupgrade_framework #5395
• web_editor - By @hbrunn - [19.0][MIG] mail+dependencies #5466
• web_tour - By @hbrunn - [19.0][MIG] mail+dependencies #5466
• website - By @hbrunn - [19.0][MIG] website #5573
• website_payment - By @hbrunn - [19.0][MIG] website_sale + dependencies #5585
• website_sale - By @hbrunn - [19.0][MIG] website_sale + dependencies #5585

Disclaimer: This will take a while, don't get excited for a working v19 migration any time soon

[hbrunn]

@MiquelRForgeFlow I see you created the 19.0 branch manually. Can we delete it and wait until this is created by OCA/repo-maintainer-conf#113? My plan for 19.0 is to make OpenUpgrade a more standard OCA repository to reduce manual work.

[MiquelRForgeFlow]

Oh, I created it because I saw some other repos having that branch, like https://github.com/OCA/server-tools/tree/19.0.

[hbrunn]

that's because of OCA/repo-maintainer-conf#112. I suggest to remove the manually created branch, and let ocabot do its thing. Are you working on something that you need this branch now? If so, we should sync because I've migrated openupgrade_framework with a few TODOs left and have a base migration that doesn't crash

[MiquelRForgeFlow]

Ok, branch deleted.

Are you working on something that you need this branch now?

I don't need this branch.

[oliverkroener]

Hello, @hbrunn is there an estimation of when the update to 19.0 will be available? Thanks for your efforts! Oliver

[vdewulf]

Hello, @hbrunn is there an estimation of when the update to 19.0 will be available? Thanks for your efforts! Oliver

Hello, the objective is to have the scripts available by February 2026 at last. The OpenUpgrade Working Group needs to organize the work and get started. It is ongoing.

To support this effort, which is partly paid by the OCA, you are invited to become a member (as well as all your team members), sponsor the OCA as a company or (soon) participate in our crowdfunding initiatives.
https://odoo-community.org/get-involved

[oliverkroener]

Hello @vdewulf thanks, that sounds great.

I have just signed up with the community organisation.

Crowd funding sounds good. Helping otherwise I am not sure, how I could do that at the moment, since the last time I had to do with Odoo was the time when it was called OpenERP, but this might change since we are using Odoo now more an more ...

Best, Oliver

[vdewulf]

@oliverkroener Indeed, I saw your payment coming yesterday. Thanks a lot for your support, very appreciated!
Financial support is always good, and of course contributing here on GitHub is helpful if you have the knowledge to help. If not, don't worry, we all have different talents and skills! As you are interested in the OpenUpgrade scripts, I suppose you/your team will be testers of the new created scripts. It's always useful to get (well written) feedback to improve them.

Lot of documentation on how to contribute technically is available here: https://github.com/OCA/maintainer-tools/wiki

All the best, Virginie

[TheMoroney]

Out of curiosity, what is the status the v19 open upgrade scripts? are they stable?

[oliverkroener]

Hello @TheMoroney I would be curious to know that, too?

[hbrunn]

it's unclear to me what kind of answer you expect here. The scripts work for the cases they've been tested on, whether they'll work for you, who knows without you testing it?