Lines Matching full:branch
34 * Set code freeze and branch creation date for 6 months after last code freeze
37 * Create release branch and begin release process.
41 fixed. Patches are merged from mainline into the release branch. Also, all
66 * Creating the release branch,
72 Create Release Branch
75 Branch the Subversion trunk using the following procedure:
85 #. Create the release branch for ``llvm``, ``clang``, the ``test-suite``, and
86 ``dragonegg`` from the last known good revision. The branch's name is
107 #. The Release Manager should switch to the release branch, because all changes
108 to the release will now be done in the branch. The easiest way to do this is
124 After creating the LLVM release branch, update the release branches'
136 ``test-suite`` by tagging the branch with the respective release candidate
335 Below are the rules regarding patching the release branch:
337 #. Patches applied to the release branch may only be applied by the release
342 applied to the branch. Code owners are asked to be very conservative in
343 approving patches for the branch. We reserve the right to reject any patch
353 branch, updating documentation that refers to the release, and updating the
364 mainline into the release branch.
