Lines Matching refs:branch

16   of new features to be introduced into the main branch when ready. Creating a new
17   collaboration branch requires a justification and TSC approval. Collaboration branches
18   shall be based off the main branch and any changes developed in the collab
19   branch shall target the main development branch. For released versions of
23 vx.y-branch
32 Changes submitted to a collaboration branch can evolve and improve
33 incrementally in a branch, before they are submitted to the mainline tree for
36 By dedicating an isolated branch to complex features, it's
41 has been completed. When a branch is requested, the proposal should include the
44 * Define exit criteria for merging the collaboration branch changes back into the main branch.
45 * Define a timeline for the expected life cycle of the branch. It is
52 Collaboration branch owners have the following responsibilities:
56 - Force pushing a collaboration branch is only allowed when rebasing against the main branch.
57 - Review changes coming from team members and request review from branch owners
59 - Keep the branch in sync with upstream and update on a regular basis.
63     branch (one-man branch).
64   - Merge requests: When a set of changes has been done in a local branch and
65     has been reviewed and tested in a collaboration branch.