RE: Migration from StarTeam to Subversion

We are currently using StarTeam and our biggest complaints about it are:
- StarTeam doesn't fully control the working copy. If Bob deletes a
file from StarTeam, then when I update my working copy, I need to
manually delete that file myself.
- The StarTeam GUI won't show directories (or their contents) that
aren't version controlled. Therefore, I can't rely on the GUI to show
me the files or directories that need to be checked in.
- The checkin structure is single-file checkin, a la CVS, as opposed to
atomic filesets, a la subversion. It has happened where someone was
checking in a set of files, only to have one of them fail the checkin.
All the other files had been checked in by this point.
- StarTeam has a built in bug tracker. However, the integration between
it and the source control system is lacking.

Just a few of the issues ...

--
Jay Glanville
> -----Original Message-----
> From: Toby Johnson [mailto:toby@etjohnson.us] 
> Sent: Sunday, May 09, 2004 11:55 PM
> To: users@subversion.tigris.org
> Subject: Re: Migration from StarTeam to Subversion
> 
> 
> Roger Talkov wrote:
> 
> >We migrated (ran) away from StarTeam last december.
> >
> Just out of curiosity, what what was wrong with StarTeam? 
> Another office 
> of ours uses it and it sounds like we might eventually go that route. 
> I've never used it thought so I'd appreciate some input.
> 
> toby
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
> 
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org