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.

How to install Plastic SCM 4.0 without system requirements restrictions

Wednesday, November 30, 2011 Luix 0 Comments

Hi, all:

As you might already know, Plastic SCM 4.0 comes with SQLServer CE 4.0 as the default backend in Windows. We decided to replace our good-old friend Firebird with this one to avoid undesired collisions with existing Plastic SCM 3.0 installations, since Plastic SCM 4.0 uses a different database schema that is not directly upgradeable.

On the other hand, Plastic SCM 4.0 minimum software requirements have been lifted to meet those of SQLServer CE 4.0 (check this link: http://www.microsoft.com/download/en/details.aspx?id=17876#system-requirements), which is a bit annoying, specially if you will customize your db.conf file to use a different backend after the installation / upgrade process.

Strictly speaking, Plastic SCM 4.0 requirements still are .NET Framework 2.0 SP2 for the server and .NET Framework 2.0 for the client (we finally moved our client to .NET Framework 2.0, hurray!), so if you want to avoid all the system requirements just open a CMD console (or shell in Linux) and type the following in a single line:

PlasticSCM-4.0.xxx.yyy-windows-installer.exe --nocheckrequirements true

where xxx.yyy is the release number you are trying to install. Please, take into account that if the system requirements are not met, Plastic SCM may not work correctly.

Thanks for reading and enjoy Plastic SCM 4.

0 comentarios:

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.

4 3 2 1... launch

Thursday, November 24, 2011 Pablo Santos 0 Comments

It has been an hectic season but we made it and released 4.0 last 17th. There has been several great things, but look at the videos: we had Robert C. Martin (of CleanCode and CleanCoders fame) and Steve Berczuk (THE Branching Patterns book) as keynote speakers!! Awesome, isn't it? http://www.plasticscm.com/plastic4launch/index-4.html Now looking forward talking, blogging and "demoing" the new release to the world! :) Thanks everyone for your support so far. We're a small, highly committed team achieving great things! :) Thanks!
Pablo Santos
I'm the CTO and Founder at Códice.
I've been leading Plastic SCM since 2005. My passion is helping teams work better through version control.
I had the opportunity to see teams from many different industries at work while I helped them improving their version control practices.
I really enjoy teaching (I've been a University professor for 6+ years) and sharing my experience in talks and articles.
And I love simple code. You can reach me at @psluaces.

0 comentarios:

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.

Git merge vs the world

Thursday, November 17, 2011 Pablo Santos , 4 Comments

I’ll be talking about git merge system again, one of the strongest on the planet, and how a good merge system can unlock a new world of possibilities for developers facing complex refactors.

And then, I’ll tell you how to break it. And what can be done.

Refactor and merge

What does refactor have to do with merge? Aren’t merging and refactors on different planets?

Not at all: you’re working on a refactor and then you need to move Class.java to a new package. It happens, doesn’t it?

But while you’re working on your refactor, I’ll be tweaking Class.java.

Ok, now refactor has to do with merging, and if you’re avoiding this situation it only means one thing: you don’t have a proper SCM (we could argue but, ok, tell me you do not need a mouse, a good IDE...).

Pablo Santos
I'm the CTO and Founder at Códice.
I've been leading Plastic SCM since 2005. My passion is helping teams work better through version control.
I had the opportunity to see teams from many different industries at work while I helped them improving their version control practices.
I really enjoy teaching (I've been a University professor for 6+ years) and sharing my experience in talks and articles.
And I love simple code. You can reach me at @psluaces.

4 comentarios: