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.431 External Release is out!!

Monday, April 29, 2013 Luix 0 Comments

Plastic SCM 4.1.10.431 (Kioto) is ready to go!

You can get the full list of changes here. Visit the Plastic SCM download page to install or upgrade your Plastic SCM client / server setup.

You also can suggest and vote new features on the Plastic SCM Forum page and tell us your opinion about Plastic SCM or use the User's Voice channel, as well.

Let's review what's new this week. Probably you'll notice some issues that you sent to us:


Performance

Update and status operations They have been improved significantly when working with cloaked items. Some figures:

Workspace with 192.818 files, 33.877 folders and 400 cloaked rules

Version 4.1.10.426
Update (Nothing to update)
With cloaked items: 644846 ms
No cloaked items: 18938 ms

Status (No changes)
With cloaked items: 326089 ms
No cloaked items: 9376 ms

Now
Update (Nothing to update)
With cloaked items: 21419 ms
No cloaked items: 18127 ms

Status (No changes)
With cloaked items: 9485 ms
No cloaked items: 8814 ms


Bugs

Fast import: Repositories exported from Git version 1.8.x or upper that included spaces in the items paths were failing

Merge to: This operation could fail when a moved to apply operation included more changes inside it.

Symlinks: Working with a Windows client, the update operation returned a "The type initializer for 'Mono.Unix.Native.Syscall' threw an exception. at Mono.Unix.Native.Syscall.getcwd(StringBuilder buf, UInt64 size)" message error when a symlink had to be removed.

Admin tool: The database migration to SQLite was not migrating the branches creation date correctly.

Enjoy!

0 comentarios: