What are the current popular source program version management software and project management software? What are the pros and cons?

Microsoft TFS:

Advantages:

1. The mission version of the requirements, project progress at a glance, for small teams, more useful than the Gantt chart

2. Integration of project management, version control, BUG tracking, to effectively implement SCRUM

3. Ability to seamlessly engage with VS

Disadvantages:

1. The entire system is implemented with ASP, the browser access is quite slow (I do not know whether the server performance is too low or my personal computer configuration is too low)

2. Access from IE, fill out a variety of development, test records, is also very slow, feel inferior to mantis BT PHP-based so convenient, fast

The 3.XP system is inaccessible, and it has to be 64-bit. So the overall performance of the computer was dragged down

The difference between GitHub and SVN

1) The applicable objects are different. Git works for developers who participate in open source projects. They are more concerned with efficiency than ease of use because of their high level. SVN is different, it is suitable for the common company development team. Easier to use.

2) The use of different occasions. Git is designed for single-project development with multiple development roles over the Internet, and SVN is suitable for the development of multiple parallel projects within the enterprise that are coordinated by the project manager.

3) The Rights Management policy is different. Git does not have strict rights management control, as long as there are accounts, you can export, import code, and even perform a fallback operation. SVN has strict rights management, which can be controlled by group and by individual for the permission of one subdirectory. Distinguish between read and write permissions. More stringent, fallback operations are not supported. Ensure that the code can always be traced.

4) Branches (branch) are not used in the same range. In Git, you can only branch the entire warehouse, and once you delete it, you can't recover it. In SVN, branch can target any subdirectory, which is essentially a copy operation. So, you can build a very many, hierarchical branch, and, when not needed to delete it, and later need as long as the checkout old SVN version can be.

5) based on the 3rd, Git is suitable for simple software projects, typically some open source projects, such as the Linux kernel, busybox, etc. Instead, SVN excels at multi-project management. For example, you can store a bsp/design document/File system/application/Automation compilation script for a mobile project in an SVN repository, or a file system that stores 5 mobile projects in one SVN. The n (number of items) * m (Number of components) warehouse must be established in Git. Only a maximum of n or M will be required in SVN.

6) Git uses a 128-bit ID as the version number, and checkout to indicate which branch, and SVN uses an incrementing serial number as the globally unique version number, more concise and easy to understand. Although you can use git tag to create some textual aliases, it is only for special versions.

7) Partial update, local restore. SVN is managed by creating an. svn folder in each folder, so it's easy to implement partial updates or restores. If you only want to update some parts, SVN can be very well implemented. At the same time the code is wrong, and can be a good local restore, of course, git can also be restored through the historical version, but it is not easy to implement a partial restore.

In short, the company's development team in the complex multi-project development, SVN is a better choice.

What are the current popular source program version management software and project management software? What are the pros and cons?