Talk:StarTeam

Database requirement

I deleted the "proprietary DB" bit because StarTeam 2005 requires the use of a third-party database such as Oracle or SQL server. .digamma (talk • contribs) reverted, claiming, "StarTeam, a CM server not a DB server, does not require the services of a 3rd party DB to operate." Please try this and tell me where I'm going wrong:

1. Start->Programs->StarTeam 2005->Server Administration
2. Configuration->New...
3. Now try and complete the wizard without creating a database on a third-party server.

--Craig Stuntz 13:46, 2 June 2006 (UTC)

I was mistaken. StarTeam does not come bundled with a proprietary database (although it may have in version 5.x - I don't recall), it comes bundled with Microsoft's MSDE - StarTeam's "default database" as selected by Borland(/Starbase?). This 3rd party database is the database I was confusing with a proprietary one. However, it will not be installed under certain selections made during the server installation process. In this case, it probably would not be a selectable option in the wizard you are referencing here.

The database requirement overview can be confirmed on p. 8 of the 'StarTeam 2005 Installation Guide' and also appears on p. 19 of the 'StarTeam 2006 Installation Guide.' So it would be more appropriate to cite in the article that a default database may be configured in addition to the 'big iron' databases of SQL Server and Oracle or something to that effect..digamma 02:06, 10 February 2007 (UTC)

Added Criticisms section

Those of us who have used StarTeam probably have some criticisms about it. I've added several to a new section and would appreciate any input from others. I'd like to maintain a neutral pov while pointing out that StarTeam does have some serious downsides to it. Also I'd like people to verify some of my claims so we can whiddle the criticisms section down if there are bugfixes for the problems I listed we're not familiar with.

--Philip Lowman 00:35, 15 March 2007 (UTC)

As far as I know...

1) Starteam only checks already declared directories; if a directory is added directly using some system tools (file manager, command line, ...), you have to add it manually. It leads to some mistakes where user forgets to add files to the repository.

2) It is very difficult to go from StarTeam to another similar tool, there is no easy way to proceed. There was a long discussion about it in some forum, but I'm not able to retrieve it. So, it can't be included in the article.

3) There is no tool allowing integration with the Windows Explorer.

4) It is not atomic; if a commit of 40 files fails after 25 files, you have to commit the 15 remaining files, ensuring you set the same comment, same label, and so on.

--Christophe 12:30, 23 October 2008 (UTC) —Preceding unsigned comment added by 159.50.249.149 (talk)

About the criticism above I have to say:

1) True until 2005R2. From 2006 on, you still have to add explicitly the new folders, but the interface shows you the so called "not in view" folders, i.e. the ones you have locally, but not in the server. The choice to add or to ignore depends on the specific project.

2) I don't understand this claim. I have used StarTeam for years, but I don't find extremelly difficult to use a subversion, for example. The concepts are the same, the commands are different. The advanced stuff can be troublesome.

3) True. They do not encourage this (I don't know why). If you want so deeply, there's a possible hack (I haven't tried myself): install the SCC integration and install a 3rd party SCC shell integration. Good luck.

4) So False. They claim to be atomic since version 6 (or earlier, I don't remember). I didn't have any problem so far, I think I'll force some kind of error some day, just in case.

All that said, StarTeam is good and such, there are difficulties: The label scheme may be difficult to understand, the branch/merge mechanism is so complex that we try hard to avoid it at all; if you choose to manage permissions at folder level, it becomes an administration hell. That's what I can remember now. --Cybermandrake (talk) 15:31, 9 June 2010 (UTC)

Security/Vulnerability

There is a outstanding vulnerability repot on securityfocus http://www.securityfocus.com/bid/28080 . Vendor (Borland nor Microfocus) did not reply to the report. There is no indication, if the exploits are limited to 2008 version, if the underlying issues were addressed in any leter release or if there are any possible workarounds. --216.185.25.243 (talk) 18:10, 22 August 2011 (UTC)

Clients

Please clarify the clients available for Starteam. The article says there's a command line interface, but not which operating system that interface runs on. - Denimadept (talk) 21:32, 9 April 2008 (UTC)

The clients are java-based, so they should run on every java-supporting operating system. Actually I heard of a colleague having difficulties running it in Linux because of some graphic(!?) dependency. I'll check.

--Cybermandrake (talk) 15:36, 9 June 2010 (UTC)

Update: Other colleague installed command-line StarTeam in a Linux box without any problem. --Cybermandrake (talk) 11:40, 2 September 2010 (UTC)

Microfocus owns StarTeam now... —Preceding unsigned comment added by 63.96.92.3 (talk) 18:59, 21 June 2010 (UTC)

Versions and Releases

• StarTeam 2009
  • Client build 11.0.0-58
• StarTeam 2008 Release 2
• StarTeam 2008
• StarTeam 2006 Release 2
• StarTeam 2006
• StarTeam 2005 Release 2

Version	Release Date
StarTeam SDK 11.0	March 18, 2010
StarTeam SDK 10.4	May 09, 2008
StarTeam SDK 10.1	February 26, 2008
StarTeam SDK 10.0	January 15, 2008
StarTeam SDK 9.3	June 11, 2007
StarTeam SDK 9.0	November 10, 2006
StarTeam SDK 8.0	April 25, 2005
StarTeam SDK 7.1	January 28, 2005
StarTeam SDK 7.0	September 8, 2004
StarTeam SDK 6.0	February 6, 2004
StarTeam SDK 5.4	September 30, 2003
StarTeam SDK 5.3	December 3, 2002
StarTeam SDK 5.2	April 23, 2002

216.185.25.243 (talk) 21:25, 28 March 2011 (UTC)