Simplifying CM: Expanding Possibilities February, 2010 SnapshotCM News

Release News

1.83 Release

SnapshotCM Release 1.83 is now available. The primary user benefit is the more powerful workspace model, allowing users to create workspaces which "mount" or access multiple snapshots. You no longer need to juggle multiple workspaces to access shared and project unique files. Rather, all related snapshots can be mounted into a single workspace for a global, unified view of the files you care about.

SnapshotCM 1.83 delivers a unified view of the files you care about, put where you want them, all in one workspace. Workspace actions, at-a-glance status indicators, and view filters operate transparently across all snapshots, even if they are in different repositories.

Other new benefits include integration of workspaces into the Project Browser, support for multiple active history dialogs, and the ability to edit workspace definitions from the workspace and project browsers.

The Project Browser now displays workspaces attached to a snapshot as children of those snapshots, as shown here:

In the picture, SSCurrent, SSCurrentIntegration and SSCurrentWork are workspaces associated with their parent snapshots. This new integration allows direct workspace selection and opening, as well as renaming. In addition, you can change the snapshot associated with a workspace mount simply by dragging it to the new snapshot.

In a similar fashion, snapshot mount locations within a workspace can also be changed simply by renaming or dragging the mount point to a new location.

1.83 Update Notes

As you look into updating to 1.83, here are a few considerations.

• The 1.83 server is largely unchanged from the 1.82.06/1.82.07 server. There is one defect fixed associated with incremental reading of changes after a directory rename. Without the fix, clients will not see such changes without restarting their client. Also, the database schema is updated slightly, so after updating to 1.83, you will not be able to roll back to 1.82.06/1.82.07 without rebuilding the database indexes.
• The 1.83 clients work with the 1.82.06/1.82.07 server, though you'll be missing the rename fix mentioned above.
• 1.83 also fixes a memory leak in the proxy server, where a few bytes are lost for every client login.
• While we usually recommend updating your repository servers first, your proxy servers second, and your clients last, this release of the clients really doesn't require that your servers be updated beyond 1.82.06/1.82.07. So you can update your clients and servers in any order.

If you have any further questions about this release, please contact us.