Who we are

We are the developers of Plastic SCM, a full version control stack (not a Git variant). We work on the strongest branching and merging you can find, and a core that doesn't cringe with huge binaries and repos. We also develop the GUIs, mergetools and everything needed to give you the full version control stack.

If you want to give it a try, download it from here.

We also code SemanticMerge, and the gmaster Git client.

Plastic SCM 4.1.10.359 is out!!!

Monday, October 22, 2012 Amalia 0 Comments

A new week, a new release: this time we're announcing 4.1.10.359 (Build 359 as we name it internally) which includes a number of bug fixes and new features!! While you can read the detailed release notes, this blog post will highlight the most relevant features and bug fixes.

Remember you can find the latest installer here.

Features

Apply local changes to CLI

So far the ‘transparent scm’ (link) was better handled by the GUI than the CLI. Now the ci (checkin), unco (undo checkout) and shelve commands can look for local changes specifying the --all option (-a).

In order to convert the local changes to checkouts, the co command (checkout) now supports a --applylocal modifier, which detects the local changes and turns them into checkouts. .

Remarks:

Only the locally moved, deleted and changed items will be handled this way. The private items must be added using the add command.

For example:

  • Command to checking all the workspace changes: the local and controlled changes
    • cm ci -a
  • Command to undo all the workspace changes: the local and controlled changes
    • cm unco -a
  • Command to shelve all the workspace changes: the local and controlled changes
    • cm shelve -a
SQL Server backend performance boost

One of the key database operations Plastic SCM performs is reading “changeset trees”. A changeset tree is the directory structure associated to a given checkin. Each time you diff a changeset, switch to a branch, merge and browse a label Plastic SCM has to load a changeset tree (in case it wasn’t cached before).

This performance improvement reduces the changeset tree load time in about a 70%, which will have a big impact especially on big repositories.

Bugs

MergeReplay: Duplicated Key

The error “An element with the same key already exists in the dictionary”, that occurs under some special condition during the merge process, has been fixed.


Enjoy it!!

Amalia

0 comentarios:

Subscribe to: Post Comments (Atom)