I think we all know that the AUH as it is currently running is useful but also has some pain points. Some of that may be improved with the changelog work but I also have some ideas about what we could do with the frequency and way the tool is running.
Currently we get a dump of all the possible upgrades and failures twice a month. What I'd like to propose is that that optionally via configuration, AUH can store some state and run in an "incremental" mode. The idea here would be to get faster notifications of new point releases from upstreams, which often contain security fixes and to reduce the size of the patch bombs it currently sends. It would track which upgrades it has attempted and sent messages about and then not send them again for some period, the exact frequency to be discussed/agreed. We'd also need to decide what frequency to update the head revision release components. Some may have different frequency to others. This would mean we could change the autobuilder job to run nightly and get a more regular stream of patches and faster security fixes. The job itself would also then faster. Does this sound reasonable? Any volunteers to tweak the code? My intent with the mail is to document/agree what I think we need, then we can at least put the bugzilla ticket and plan together whilst we work out who can help make the changes. Cheers, Richard
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#2349): https://lists.openembedded.org/g/openembedded-architecture/message/2349 Mute This Topic: https://lists.openembedded.org/mt/119311463/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-architecture/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
