Perforce Streams: Everything You Need to Know

[@Grand_Alchemist]

I'd appreciate some insights on best practices. Currently, I'm working with a third-party codebase template, which forms the foundation for two distinct projects of mine. My aim is to establish this codebase template as the mainline stream. This way, whenever there's an update from the original developer, I can seamlessly update the mainline stream and subsequently merge these updates into the development branches of my projects. The key idea is to facilitate smooth updates to these branches whenever the third-party codebase is upgraded. Considering this, I was contemplating setting up three separate depots: one serving as the mainline for the third-party codebase and the other two as development streams branching from this mainline. Additionally, I plan to have release streams branching from these development streams instead of directly from the mainline. Is this a structurally sound approach? Would this setup effectively support updates across my projects while maintaining clear separation between them?

[@x007-w7g]

A nice video， I also want to know more details about import，exclude and component feature using in mutiple branch

[@coltish]

It's almost like Jase listens to the community... hmmm and he's a good actor... something's up! Jase Lindgren is up!

[@DanielHeeris]

Really nice overview Jase, I've been a Perforce admin for 15 years, but always learn something new from your videos :) I was wondering if there is any automation to help with the naming of Tasks streams available out of the box? Like autofill with a job name, or jira ticket, or even just an incrementer, from a trigger on the server or even client side.

[@x007-w7g]

does the stream component support to merge in the big stream? The import+ stream does not support this feature, what diff between them.