QVCS-Enterprise 2.1.20.2

• Affordable, cross-platform version control for local or remote teams.
• Supported on Windows, Mac OS X, Linux, and Solaris.
• Easy to use GUI client
• Works well over the internet.

Major Benefits:

QVCS-Enterprise makes it easy to:

• Get your development process under control.
• Coordinate file changes with off-site developers.
• Use a single version control tool for your Linux and Windows developers.
• Have confidence that you can recreate a past release.
• Create reports to show what has changed since the last release.
• Create a report to show what files are contained in the last release.
• Create a patched release of a product.

Why buy QVCS-Enterprise instead of QVCS or QVCS-Pro?

• QVCS-Pro and QVCS are both great tools for Windows developers working alone, or Windows developers working in small teams at the same location. But what if some members of your team don't share the same office location? This is where QVCS-Enterprise really shines. It's designed from the ground up to provide excellent performance for geographically distributed teams.
• QVCS-Enterprise is also a great fit for teams that use Linux, or use Linux, Windows, and other platforms. Because QVCS-Enterprise is written in Java, it can run on any platform that has a 1.5 (or later) JVM.

What's Included:

• The QVCS-Enterprise product includes the server, a client application, an IDE client .dll (for Windows only), and a separate admin tool.
• These applications can be deployed on a single machine (when working alone, for example), or on separate machines, as required.
• On-line documentation is included with the server and is 'published' by the server via a simple built-in web server.
• QVCS-Enterprise licenses are sold per concurrent client. IDE integration counts as a client, so running the client application and IDE integration at the same time counts as 2 users.

Major Features:

1. Store/retrieve file revisions.

2. Insert keywords into your source code or binary files for automated documentation and audit trail generation.

3. Keep track of who changed what, and when they changed it.

4. Enter a comment at checkout time. That comment becomes the default comment at checkin time.

5. Label revisions for a release.

6. Restore a project to an earlier labeled release.

7. Control modification access to files at the project level.

8. Use built-in visual compare tool to compare files to earlier revisions or compare revisions to other revisions.

9. Create a parallel development branch (branching).

10. Easy migration from QVCS or QVCS-Pro.

11. Create a variety of reports including:

• report all locked revisions
• report all revisions locked by an individual, or set of individuals
• report all revisions created after a release
• report all revisions created by a single individual, or set of individuals
• report revisions created between two dates
• report all revisions that have a given label
  report any AND'd combination of the above

12. Show at a glance all local files that are different from the latest checked in revision.

13. Define named file filters to easily filter the set of files that will get displayed.

14. View all the files of a single project within a single file list.

15. Drag-and-drop a single file selection from the file list onto any target that accepts a file.

16. Use drag-and-drop to move a single file from one directory to another within the same project.

17. Rename a file.

18. Create a read-only date based view so you can see what a project looked like at some time in past.

19. Create a read-only label based view.

20. Create a read-write label based view so you can easily create a patch release of a product based on an existing label.

21. Manage user roles at the project level using a separate, secure admin tool.

22. Use a fine-grained authorization model to govern which users are permitted to perform various actions.

23. Use custom Ant task to perform bulk 'get' and 'label' operations.

24. Connect to the QVCS-Enterprise server via the Internet, VPN, LAN, or locally.

25. Define and enable file groups so that selection of one member of the file group will automatically select all members of that file group. (A file group is a set of files that share the same file name, but have different file extensions).

26. If installing the server on Windows, you can run the server as a Windows service so it starts automatically when your Windows server machine boots up.

27. On Windows platforms, integrate with IDEs that support Microsoft's SCC API. This includes Microsoft's VS 2005, VS 2003, VS 6.0, VB 6.0, Sybase's PowerBuilder, and others.

Enhancements:

1. Add client API;
2. Improve SCC support including VS2008;
3. Other minor changes and bug fixes

Requirements:

1. Java J2SE 1.5 or later.
2. Server machine should have 512 Meg or more.
3. 20 Meg minimum disk space for applications and archives.
4. Client machine(s) should have 384 Meg or more.
5. IDE integration (Windows only) requires a user supplied IDE that supports Microsoft's SCC API.
6. Supported on Windows, Mac OS X, Linux, and Solaris platforms.

WareSeeker Editor