* The version number won't change in a branch (although it may be time a revision ID was included in the version information pushed back up to the host);
* The firmware API and behaviour must not change along a branch;
-* A branch update must not require an ath9k_htc driver update to function. It may go hand-in-hand with some vendor patches to ath9k_htc to fix some particular issue, but the firmware must still function on the latest version of ath9k_htc which is paired with the branch version.
+* A branch update must not require an ath9k_htc driver update to function. It may go hand-in-hand with some vendor patches to ath9k_htc to fix some particular issue, but the firmware must still function on the latest version of ath9k_htc which is paired with the branch version;
+* Any fixes to a branch must first be applied and debugged in master before backported.
+* .. ie, features/fixes must not go into a branch first.
If not - the branches themselves will just stay what they are - indicators of when things were released.
\ No newline at end of file