Create a baseline
Have you just finished importing your initial code into Plastic? Is it compiling? Is it ready to be shared with the rest of team members? If so, it's the right time to create a baseline!
What's a baseline? Very simple: a label. It's a snapshot of your code at a given point in time, a mark, a tag you can use to rebuild this status later (ok, there are other ways like using changesets, but this is the best one).
A label is just a human-friendly name that you assign to a specific changeset, so what you are labelling is indeed the state of your code at a specific branch and point in time.
To create a label follow these steps:
- Open the labels view by clicking on Labels inside the section Other actions in the left panel of the GUI.
- You will see the labels view (with all the labels you've created so far, if any). Click on Create new label and a window like this pops up
- Type the new label name and comment.
- The changeset to label is the most important field. It tells Plastic where the label is being applied. The default value is the current changeset loaded in the workspace, so you are applying the label to the versions of items that are in your workspace and are checked in. Nothing prevents you from selecting a different changeset, if you know that you want to label a different state.
Now you've created a new baseline.
About label naming conventions
Labels are very important to keep your project running smoothly. Avoid weird or meaningless names and try to come up with a well-defined naming convention.
We at Codice name every new release as BLXXX (from BaseLine): BL000 was the first ever Plastic internal release, and BL187 was 3.0. Every time we create a new internal release (which should be done frequently) we label the entire project.
So I suggest you decide on a good convention for your team, and apply the labels accordingly.