I'm sorry if this is not the right place to ask, and feel free to move my post to wherever you want to... because this is not a, let's say, technical question. Or it is. I don't know...
My question is: what is the "workflow" that a snapshot takes in order to be promoted to a release state?
I'm asking particularly for the new devices that became supported recently.
Snapshots are just automatic daily test builds. Releases are done from special release branches, but have no relation to the master snapshots.
Usually new devices are just added to the master branch that is used for master snapshots. When a new release branch is created for the new release series like 19.07.x, the devices in master at that time get shown in that new release branch.
The new devices added later into master do usually not get backported into the old release branch. E.g. some new device created in master today would not get into 19.07 branch and would thus not be in 19.07.3 (if that gets built). The device would be in the next forthcoming 20.0x release series. (To large extent the 19.07 branch will continue to have the devices that were supported in June 2019)
Sometimes new devices are backported into the release branches by the devs, but that is not typical.
Thanks for the explanation (although I realize now that the way I wrote my question wasn't so clear).
If I understood well, this commit, for example, that adds support for the V3 version of TP-LINK Archer C60, will be in the master branch and therefore released when the 20.x version came up, right?