From e06471bfb8b055028c00322f1d35f04c699331aa Mon Sep 17 00:00:00 2001 From: erikarn Date: Wed, 27 Mar 2013 14:54:39 -0700 Subject: [PATCH] Updated BranchPolicy (markdown) --- BranchPolicy.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/BranchPolicy.md b/BranchPolicy.md index 35d5387..5d3460a 100644 --- a/BranchPolicy.md +++ b/BranchPolicy.md @@ -17,6 +17,8 @@ The branch rules: * 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 -- 2.25.1