What arguments can be made for the client / boss for SUN Teamware & # 8594; modern SCM migration?

The team I'm working on is still using SUN Teamware for source control (SCM). I worked with him for a while (more than 10 months), and I have no particular complaints about this.

Teamware is used to manage the largest Suns source trees, including the Solaris operating system and the Java system, and works very well. But it is also an old commercial (closed source) product that has been discontinued. This became part of the Sun process, turning its codebases into open source communities, which in turn led to the transition to newer version control systems such as Mercurial.

It makes me feel like we're stuck on time using Teamware and the world has moved to newer systems. However, I do not miss any specific functions, with the possible exception of having a web view of the source tree for navigating and viewing file history (something that we do with VersionTool is therefore not critical).

Should a team using SUN Teamware move to a more modern SCM, such as git or Mercurial?

And more importantly, what arguments can you present to the rest of the team to support this transition?

+3
source share
3 answers

SCM, , , . Teamware , .

+2

, Sun:

VCS Sun Teamware Solaris?

, , .

Git Survey 2007-2008.

+2

, , , , . , SCM .

, git/Mercurial/Bazaar .

0

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


All Articles