Question about which releases/branches to target with package-updates.
I was looking into the Zabbix package which is at v6.x for OpenWRT v23.05.x.
For OpenWRT v24.10.x this will be Zabbix v7.0.0. Already a nice update!
If i would want to update the Zabbix package to v7.2.2. I guess i would then target the master-branch. But that would mean that the current stable OpenWRT package versions will lag behind for maybe 6 months. This probably is not the biggest of "problems", but "we" want everything always "now".
Will there updated packages be backported from Master-branch to v24.x-branch? Or should devs create a seperate Pull-Request for this?
Just trying to get a feel of the development flow..
The general procedure is to make all updates on main, so they get into the snapshot builds. If there are no blockers, like ABI changes or whatever, then you can simply submit another PR that uses git cherry-pick -x [commit-hash-on-main], one for each release branch you want to support. If you need to make code changes, then you do a fresh PR on the release branch.