Clarify stable branch process in contributor documentation
Explicitly mention that changes known to be needed for a specific release should be pushed for review on that release's stable branch. Change-Id: I5b90edb2635495493639e181741eea111ca30d7b
This commit is contained in:
@@ -271,6 +271,10 @@ From time to time bug fix releases are made for existing stable branches.
|
||||
Developers concerned with stable branches are encouraged to backport or push
|
||||
patchsets to these branches, even if no new release is planned.
|
||||
|
||||
Fixes that are known to be needed for a particular release should be pushed
|
||||
for review on that release's stable branch. It will then be included in
|
||||
the master branch when the stable branch is merged back.
|
||||
|
||||
|
||||
GERRIT
|
||||
------
|
||||
|
Reference in New Issue
Block a user