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

Monday, March 11, 2013 Luix 0 Comments

Today I've just published the Plastic SCM 4.1.10.411 (Gotham :-D)!!

For a detailed listing of all changes, refer to release notes. I recommend to visit Plastic SCM download page to install or upgrade your Plastic SCM deployment.

As usual, you can suggest and vote for new features on the Plastic SCM Forum page and tell us what do you think about Plastic SCM. Don't forget the User's Voice channel, too.

Ok, now, let's move on to explain the most important features and bugfixes included in this release:

New features

Mantis extension
Some users were experiencing problems with tasks titles that included special characters, when listing them in Plastic SCM. This is now correctly handled and shown in the GUI.

Synchronization view
The sync dialog now tells you the repository of the branch that is being replicated. This is quite useful when you are synching lots of branches coming from different repositories.

In addition to that, we have disabled the "close dialog" button to avoid undesired effects, since it is not a good idea to interrupt a replica in the middle of the process. The situation is correctly handled, but it doesn't make much sense to interrupt it, don't you think so? (unless some network problem happen, you know :S)

Now, the bugfixes:

Bugs

Synchronization view
Again, we have made some little but noticeable improvements in this view. In this case, there was a problem when pushing a branch and clicking on the Retry button after some kind of failure. It was showing an incorrect progress in the operation.

Merge
The following is quite a weird case, but that could happen anyway: when a full check in was performed from the CLI with no xlinks involved and there was some moved items and there was a checked out item without changes, the check in command failed with a null message. The operation finished correctly, but we've fixed the message issue and closed the operation correctly.

One more: when a delete operation was undone during a conflict resolution, an unneeded File System protection operation could take place (if working with File System permissions). This is now fixed: the unneeded File System protection operation has been removed..

So, I hope you enjoy this new release. See you next Monday, hopefully, with a new funny city... Metropolis, may be? ;-)

Luix

0 comentarios:

Subscribe to: Post Comments (Atom)