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.

Release BL063.2 is out!

Wednesday, August 08, 2007 Pablo Santos 0 Comments

We've just released Plastic SCM 1.5 Build 63.2 (BL063.2 internally). We've been basically focusing on usability, trying to solve some issues which were not clear enough.

The first improvement is the ability to select a repository to work on when creating a workspace. Before you had to first create the wk and then switch to the branch on the desired repo or manually edit the selector. The workspace creation dialog now lists all the available repositories and lets you choose one.

Another small improvement (but it seems to have a big impact in usability) is showing the repository you're working on in the GUI tool status bar. You know Plastic is able to mount more than one repository in the same workspace, but in most cases people just uses a one to one relationship between workspaces and repositories. For them knowing exactly where they are working on is a big step ahead.

And finally we've included a capability into the merge dialog which was only supported by the command line client so far. Imagine you're working on a given branch, starting from a given release. Meanwhile the rest of the team advances to the new release and you're still working so your code won't go to the release, but you're still interested in getting synchronized with the latest changes, so you would need to merge from the release. Now the merge dialog makes it really easy.
As the Plastic user base keeps growing we try to focus on solving the usability issues they report. Usually a pretty small change in terms of coding effort, makes a big difference for users, as these three changes clearly show.

0 comentarios: