"Best practice" depends on your workflow and setting up your branches. There is really a good time for one change list to contain all integrated change lists - we do this quite a bit in our studio when creating "functional" branches, and the branch needs the latest and updated trunk code. On the other hand, integration in the change list can be very useful at the end of the product cycle, when you need to fork certain fixes or functions into release branches.
Integrating with the change list is simple:
- Locate the list of changes you want to send in the "submitted change lists" panel (ctrl-2)
- Right-click the change list and select "integrate using the submitted NNN change list"
- Set any parameters you need in the next dialog box.
From there, you can preview and / or run the integration. As a hint, I always look at the integration first. This will indicate potential errors or warning conditions that you might encounter before performing the actual integration.
This method of integrating the change list is currently called "cherry picker." Perforce has an excellent cherry change list knowledge article here .
Mark source share