Jump to content

Best practice Stream for developing a feature

Stream Depot Workspace

  • Please log in to reply
1 reply to this topic

#1 pdsavard



  • Members
  • Pip
  • 1 posts

Posted 27 March 2017 - 08:11 PM

Hi expert!
We are starting to use the Stream type Depot, we currently use one Depot by large projects. Normally, we are using these streams:

- Release
- Main
- Dev

What is the best strategy to manage Feature Branching? For example, we need to create a new module, we will create a Development type stream under DEV (Feature1) then work in it. When the feature is completed, we will merge DEV->Feature1 then copy Feature1->DEV. At this point the branch Feature1 will no longer be needed. What can we do? Delete the workspace and delete the stream?

What is the best practice?

#2 CarolineB


    Advanced Member

  • Members
  • PipPipPip
  • 44 posts

Posted 29 March 2017 - 09:11 AM

Well you can imagine several solutions, depending on your environment & constraints

You could for instance use a Task Stream for your feature development; that means you would not be able to create some dev streams from this stream. Once the work is done and copied up to the main stream, you can unload your Task stream, and if really useless, delete it after a while. You could even locate your Task Stream in a separate streams depot, storing streams, provided you are not interested in turning your Feature Task Stream into a dev stream (for any good reason :))

You could also recycle your stream, once the job is done. You can change its name, if need, and decide to work on another topic in the dev stream, even, possibly, modifying its definition/mapping.

You could also play with your protection table, making your feature dev stream unreadable by all users, when it is not needed anymore.

You see, there are multiple solutions (it is not a complete list of solutions, for sure), depending on your needs/contrainst :)

Also tagged with one or more of these keywords: Stream, Depot, Workspace

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users