RFC : Generating the analysis files automatically in a cronjob

[legalsylvain]

Hi. following the proposal of @hbrunn here.

I'm also looking into generating the analysis files automatically in a cronjob so that we always have the latest analysis on github without human intervention.

I propose to talk about that interesting topic here.

rational : (if I understand correctly, correct me if I'm wrong @hbrunn ).
(Exemple : 17.0 -> 18.0)

• The analysis files are generated at the beginning of a new Odoo version, with the upgrade_analysis module, that is in OCA/server-tools. https://github.com/OCA/server-tools/tree/18.0/upgrade_analysis by any Openupgrade maintainers that is initializing the project
• Then, the analysis file are correct, but version 17.0 and 18.0 will continue to have patch / changes in odoo core. Some changes requires to update the analysis file. Current Odoo policy say that changes are possible during 3 years. (https://www.odoo.com/documentation/master/administration/supported_versions.html)
• After few monthes, so, the analysis files are obsolete and should be updated. For the time being, updating analysis is done manually See for exemple @MiquelRForgeFlow PRs : V16 PR V15 PR, etc..
• This action could be done regularly by a bot.
• however, if an analysis is updated on a "done" module, openupgrader should manually check if there is extra changes to do.

Proposal

• Having a github cronjob on each openupgrade version (that is maintained by Odoo SA), to generate regurlarly (Each 3 monthes ?), new analysis and create a PR.
• in the text of the PR, generate a message, that contains the list of the modules that has been changed AND that are marked as done (or Nothing to do).

Question : if the PR is created in an OCA branch, only maintainers can work on it. (maybe it's not a huge problem...)

what do you think ?

CC : @OCA/openupgrade-maintainers