This file describes the changes in QVCS 3.x that a user of QVCS 2.5 will want
to know.

Summary of Changes
~~~~~~~~~~~~~~~~~~
1.  QVCS logfile format is identical between 2.5 and 3.x.  There were absolutely
no changes made in this area.  This means that 2.5 and 3.x can inter-operate.
If you have some users who prefer to stay with the 2.5 interface, they can do
so.

2.  QVCS 3.x is a 32-bit only release.  I have no plans to migrate the 16-bit
version of QVCS to support the added features provided by 3.0.

3.  The 3.x GUI is completely re-written with a completely new look that you'll
hopefully find easier to use.

4.  Some of the information shown on the "module" tab in 2.5 is not shown on the
3.x GUI.  You can still access that information by using the qlog command line
utility.

5.  The 3.x GUI supports "recursive" operations for most commands at the project
level.  For example, you can "get" an entire project directory hierarchy by
doing a project level "get" on the root directory node for that project.

6.  The 3.x GUI supports a new "report" (history) window that can be sorted and 
filtered.  You can "print preview" the report window, as well as print a report
showing its contents.  This is a powerful feature that makes it easy to find
revisions or sets of revisions that meet a set of criteria that you define.

7.  3.x does not support "user" projects.  3.x however does allow you to define
workfile locations for a project on a user by user basis.  To migrate 2.5 user
projects to 3.x, you must MANUALLY copy the project settings from your 2.5
user .ini file into qwin.ini.

8.  For command line users, project settings are now matched by workfile location
instead of by logfile location.  This should make things easier in general, but
it you WILL have to re-work any batch files if you have logfile and
workfile locations anywhere but the QVCS default locations for a project.

9.  There are many, many other changes in the product, many due to your feedback.


Thanks to all of you for your suggestions.  My goal is for QVCS to remain the best 
version control value on the market.


Jim Voris, President
Quma Software, Inc.
jimv@qumasoft.com

