500 is the number
Hey buddies, you know what? We've reached the number of 500 releases!!
I'm not authorized to give you free licenses to celebrate it, but... I'll hand to you a brand new release with several improvements and bugfixes. Sounds good?
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.
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.
RedMine Integration
We are announcing Plastic SCM integration with Redmine project manager. As you probably know, Redmine is a flexible project management open source web application.
We have to thank Wonho Seo for developing this plugin. He is a Plastic SCM user who has decided to create a custom integration for RedMine. He has published the plugin using GPL license and you can download it at:
https://code.google.com/p/redmine-plastic/
You need to download two files:
- redmine_plastic-1.2.2.zip: contains the plugin you need to install on your Redmine server.
- RedmineExtensionVS2008.zip: contains the source code for the Plastic GUI integration.
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 and Plastic SCM 5.0 fresh meat
Hi, everyone!
Today I'm announcing two new releases:
- 4.1.10.493 in our Public section.
- 5.0.43.495 in our Labs section.
There are rather small but noticeable fixes that will help you enjoy Plastic SCM a little bit more.
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.
Semantically diffing Java code
Knuth stated that source code is meant to be read by humans, not machines. Code is going to be read by our peers more often than it is going to be modified and that’s why keeping it clean and well organized is key.
But cleaning up code very often means restructuring the sources in such a way that reviewing the changes becomes a nightmare with conventional diff tools (not to mention merging). And at the end of the day the outcome is that clean up is postponed or only performed during “refactor specific” tasks which tend to be much less frequently scheduled… negatively impacting the technical debt.
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 Semantic MethodHist is now out!
IMPORTANT: Take into account that the Plastic SCM installer in .NET 4 explained below will not work with the "regpkg" mechanism in Visual Studio 2005, 2008 and 2010, so be advised that the Visual Studio package won't work in those versions. This is due to the target framework used in this installer: .NET 4 is much newer than Visual Studio 2005 and 2008, and regpkg don't work in VS2010 with .NET 4 assemblies. For this reason, use Visual Studio 2012 and 2013 to use Method History from the IDE.
Have you heard of the new CodeLens in Microsoft Visual Studio 2013 + TFS? Well, we’ve just released “Semantic Method History” which is… well, CodeLens done right!
We’re very happy to announce Method History since it is the first application of the SemanticMerge technology inside a core Plastic SCM feature and we think it will be the starting point for many more exciting new features.
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 release 5.0.43.483 is out
Hi Plastikers,
We’re glad to announce a new 5.0 release! It has been out for a few days under “labs” in our website but we’re just announcing it now in the blog.
This release comes with a big number of improvements and bug fixes but the most notable one is the Branch Explorer support in Eclipse:
Subscribe to:
Posts (Atom)
0 comentarios: