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.

New version of SemanticMerge is out - 0.9.22

Thursday, May 09, 2013 0 Comments

Here we go again with a new release of SemanticMerge, the merge tool that understands your code (and maybe reads your mind too :P).

While we work on the next major release we’ve finished a few small but important changes ready to be published on our weekly version (I should better say the next two major releases since we’re already working on the biggest request on user voice :-O).

Let’s see what’s new on SemanticMerge 0.9.22.

Update system with built-in release notes

Yes, now when a new upgrade is ready, the upgrade window will show you what is new...

We’ve also added a --nocheckupdates flag so that you can avoid looking for fantastic updates... just in case.

If you decide to “update” then once you launch the tool you’ll see something like the following on the bottom right corner.

And once the download is finished it will give you instructions to restart:

We think the built-in update system will save precious time and will help all users staying up-to-date with the new versions.

SemanticMerge issue with “not valid license” message

Last week we launched support for Vb.net and since then some people experienced the following error: starting the diff tool they started to get a “not valid license” error message.

In fact the error was not really related to the Vb.net release but to the fact that the diff tool is not able to “request a new license” and that some people downloaded this new version just 15 days after downloading the first one, exactly when the built-in trial expired (Vb.net was launched 15 days after the initial c# launch).

Well, now it is fortunately fixed!

Encoding lost saving the result file

This is one of the bugs fixed on this release. There were issues keeping the encoding on the result file and it has been fixed now.

Fixed issues in conflict resolution

When conflicts had dependencies, there were issues solving them due to an internal cache update. It has been fixed too.

Next steps

We’re working on a number of features right now. We’re getting closer to release Java support, which is going to be the next big launch. We expect it to get really big since Java is one of the most widely used programming languages.

We’re also working on Mac OS X support. We guess we’ll need to add good Javascript support too in order to make the Mac OS X version really usable, and JS is top 3 request in uservoice as I write this.

But, we also think adding Mac OS X support will be great for all the Xamarin Studio users getting advantage of C# to develop for Mac, iPhone and even Android! :-). So let’s see what we can do to have it ASAP. We will be using the SemanticMerge Mac OS X development as test field for the upcoming Plastic SCM GUI for the Mac. We will be publishing the drafts of the Mac OS X Semantic Merge GUI soon, so you can give us early feedback.

The top 2 request is support for Linux so I’d love user feedback on your favorite GUIs for Linux.

We also need to move fast to support C, C++ (I guess we’ll be able to have C support earlier than C++ since it is simpler) and later Objective-C, but it will take a little bit longer.

We’d like to finish some proof of concept of “multi-file” SemanticMerge, which is also one of the super big features to come, but right now we’re fully booked. Remember we’re also releasing new Plastic SCM versions regularly each time ready for bigger and more complex companies.

Of course: we will be releasing support for fully automated SemanticMerge soon (not having to answer any questions if the merge can be automatically solved, as an option).

And one final note: we’re working on an astonishing “semantic visual diff” which will be able to render the differences visually, to better understand what is going on with your really complex refactors!

Social bar

Many of you have noticed we added a “social bar” to the SemanticMerge GUI. The goal is to help us (in fact help you helping us!) spread SemanticMerge so it reaches a wider number of users. It hasn’t been successful so far although people twits about SemanticMerge really often, but not using the tool.

Do you think it would make sense to add some sort of request to tweet when you finish a very complex merge?


If you’re already using SemanticMerge the update dialog should show up the next time you run it. If not, don’t forget to visit www.semanticmerge.com.

0 comentarios: