Lines Matching full:branch
29 there are large number of bug-fixes in the stable branch or a critical bug
37 * Set code freeze and branch creation date for 6 months after last code freeze
40 * Create release branch and begin release process.
44 fixed. Patches are merged from mainline into the release branch. Also, all
73 * Creating the release branch,
79 Create Release Branch
82 Branch the Subversion trunk using the following procedure:
92 #. Create the release branch for ``llvm``, ``clang``, the ``test-suite``, and
93 ``dragonegg`` from the last known good revision. The branch's name is
114 #. The Release Manager should switch to the release branch, because all changes
115 to the release will now be done in the branch. The easiest way to do this is
131 After creating the LLVM release branch, update the release branches'
321 Below are the rules regarding patching the release branch:
323 #. Patches applied to the release branch may only be applied by the release
328 applied to the branch. Code owners are asked to be very conservative in
329 approving patches for the branch. We reserve the right to reject any patch
359 branch, updating documentation that refers to the release, and updating the
370 mainline into the release branch.
