we are doing our first branch of a project, and need some help (used to do it with source safe...).
We need to start from a label made some days ago (done with 'show labels...' then share): worked fine.
However, as the parent project is pinned; there is nothing we can do without 'unpinning' the parent and having all the files returning to a shared status, then loosing the version they were supposed to have.
This is exactly the same if we would like to merge the branch: it fails because the project is pinned.
So unless I'm wrong, once a project is pinned there is nothing we can do (beside unpinning it and loosing its version status) ? So what's the use of this feature ? Having a quick view of a label ?
If we decide to branch the project, I suppose that all files will be branched; which is also not what we want. We want to be able to either branch a single file of the branched project to do a specific fix without getting all the new stuff, or pin it to another version that may only have a fix.
Is it possible ?
I've read the help, but it's unclear on how you designed it (label branch), how we are supposed to use it.
I think this is the very basic need:
- have a stable version on which we might provide some fixes/service packs (so have most files pinned to a version of the main branch, and some branched)
- have a 'current' version with as many bugs as there are new features
![Wink ;)](./images/smilies/icon_wink.gif)
- sometime, with a merge branches, copy a fix from the current version to the stable one.
Besides this pinned project that prevent to do anything, it seems the merge is very pratical !! (sourcesafe is so awful when it comes to merge files...)
Looking forward to some clue, advice on how to use it.
Last question: How can I rename the branch (pinned project), we used to name them by their version : Project_v1, Project_V2, while the current version is named Project
Regards