- .polarion (automatically created by Polarion)
documents (automatically created by Polarion)
This makes a problem when accessing the project work items via FastTrack. It forces the user to check out the full project tree with ALL branches and tagged versions.
Now my question: what is the recommended layout of a Polarion project that has already existing source code?
Any better idea?
For my opinion it would be OK to use a layout like:
This would allow to tag a current state of work items as well as of source code. But will the polarion 'auto-link' feature to the svn commit message work with such a layout?
And how can I change project directory layout afterwards?