@jow suggested I ask (@tmomas/@bobafetthotmail) here about a number of devices which are supported on 19.07.0 by ar71xx but not yet ath79. It seems that a number of device pages for these devices is still showing current supported release as 18.06.x.
Is there some automation that goes on to fill all of the device pages with supported releases that is not accounting for this ar71xx/ath79 split or does somebody actually go through all of these device pages one by one updating them piecemeal?
Should we (users) update current supported release fields when we see them being inaccurate or will such automation above just come by and wipe those updates out reverting them back to their pre-updated values again?
Yes, the update of the dataentries is done via script.
If target = ar71xx-ath79, then create new release download url out of snapshot download url (ath79).
If release download url (ath79) does not exist -> do not update to new release
Depends on the number of affected devices.
If the number = low (20 something I'd say) -> Yes, please update the dataentries as needed!
If the number is higher, I can possibly adapt the script and run it again, in order to get ar71xx-ath79 devices which have not yet received an update due to missing ath79 download url updated from 18.06.5 -> 19.07.0 (ar71xx download url)
The scripted update will not wipe any information.
That's my thinking also. Better a 19.07 ar71xx release than the existing 18.06.x release those devices currently point at.
Oh, that would have been a pity. Would have left a lot of devices out in the cold, unnecessarily. I can completely understand the desire to move to ath79, but if a device is not there (yet), not providing any 19.07 firmware for it all would have been worse than it staying on ar71xx (IMHO) -- at least until it could be ported to ath79.