Create a new task branch.
It's really simple:
- Go to the Branch Explorer (you can achieve the same from the Branches view).
- Select the parent branch (typically /main).
- Right click on it and select "Create child branch".
- Enter the new branch name (related to the task, remember naming conventions), comment, and select the right base: the last stable baseline.
- ... And you're done!
The following figure shows the Branch Explorer and the main branch context menu.
Note that Plastic is able to keep track of branch hierarchies. What's that mean? It's all about the pattern we're following. You make a branch for each task, right? Well, each of these new child branches will be integrated back into its parent when you're finished.
It's very important that you give each branch a meaningful name, typically following a naming convention. In the example above, I named it task0142, which means it's the 142nd task in the associated issue tracking system.
You can see in the image above that I wrote a comment. It's not mandatory, but I do personally like to copy the task headline into the comment (something that can be automated with a trigger, by the way).
The most important part of this dialog box is the branch base, which means where the branch starts from. There are several options to define branch inheritance, but for the sake of simplicity we'll stick to the first one: select a well-known stable baseline as the basis for your task branches. In the case above, I selected Label and used Release_0.6.
Take a look at the Branch Explorer now to see what it looks like after creating your branch.