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.

Listening to the user voice

Wednesday, January 04, 2012 Pablo Santos 0 Comments

Happy 2012 everyone!

You know we listen to you and here’s a blog post focused on explaining what’s new in our latest BL237.7 build ( version) and where does it came from.Remember we’re using “user voice” and we’re more than happy to receive your feedback there.

The top one request: create branch from my checkouts

You wanted it and here it is the result:
(The entry was introduced in “uservoice” only 20 days ago!)

Gamer’s choice: undo unchanged

I got this one (again) during my “US Tour” about one month ago. Gaming companies seem to dramatically need it, and here it is! :)

Never miss the switch

Another “classic request”: you create a new branch, then you want to switch to it. Why Plastic doesn’t have an option to do it in one step? Ok, here it goes.

More requests

If you check BL237.7 release notes, you’ll find it is filled with requests and fixes. Just to mention a few:
  • New: Xlink creation from a label. Example: cm xlink codesecondrepo / lb:LB001@second@localhost:8084. I promised this one a few days ago on the forum, didn’t I?
  • Provide a way to “ignore changes” so that they’re only considered if they’re checked out! (Reminds me Salt Lake City! :P)
  • Branch explorer label menu: if there’s only one label, don’t show a sub-menu
  • Merge: able to specify “merge contributor” from a context menu
  • Merge: able to correctly merge (and visualize!) chmod protection changes
  • Enhance top level branch creation (top level branches were almost evil in 3.0, but they’re your friends now… I’ll blog about it soon)
  • New “rm-rep” trigger: new trigger available: before-rmrep and after-rmrep, executed when deleting an existing repository

    And fireworks to finish

    This one deserves a post on its own: do you know that Visual Studio “move tracking” is greatly limited? If you move a file from one project to another within the same solution… it won’t work. Visual Studio can’t handle this and will incorrectly notify an add/delete pair instead of a move operation to the underlying version control. It was broken for infamous SCC and it is still broken now, including TFS.

    Well… we fixed it! New 237.7 is able to deal with files moved between projects!! Cool, isn’t it!

    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: