All geek questions in one place

What is a good way to branch specifications along with code using TFS and Sharepoint?

We are a company with a software product, and our product code base naturally branches out for different projects. We are currently using TFS2008, which is configured to store documents in SharePoint 2007. Both of them will be upgraded to 2010 versions starting with TFS.

We would like to share, not just the version, our specifications, so that any release from any code branch can be tested against the corresponding version of the specification.

It seems to me that we can:

  • Save our specifications to SharePoint using SharePoint Search and Versioning, and tamper with the branching problem using naming conventions or subdirectories
  • Move our documents from SharePoint to TFS. Enjoy the free version and fork and calmly cry about our lost support for SharePoint document management.
  • Find any magic plugin that gives us the best of both worlds?

Does anyone have experience with any of these options?

+3
source share
3 answers
  • Using SharePoint is a big advantage because it's easy to access \
  • Having documents in TFS is a big advantage because code and documentation are synchronized for each version.

. , , , SharePoint TFS. -, , SharePoint.

, TFS , .

0

, 1, : , , MS Word . .

, , - 1, , .., Sharepoint.

0

, , .

-, :

[1] Word 2007, SharePoint Word (: p > > > ...) [2] Word (: p > > > ...), TFS, barfs .

TFS, ( TFS 2008 ), [2] , ( ) - , -.

:

, SharePoint , TFS.

If this requirement arises, we can copy a snapshot of the related specifications in TFS when the branch is released, but I hope that either the forked specifications will not change the date after the release, or if they do, SharePoint versioning will be good enough for us.

0
source

Source: https://habr.com/ru/post/1763613/

More articles:


All Articles