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 BL063.3 is out!

Wednesday, September 05, 2007 mdepedro , 0 Comments

We have just released Plastic SCM 1.5 Build 63.3 (internally BL063.3), we have focused on correcting a few bugs but we have also introduced a couple of new features:

The first one is our Advanced Query System (AQS) which is available through the command line interface (cm query command).
If offers a more complete option to our Simple Query System: if it is in your repository, our Advanced Query System will be able to give you the information!
The new system language is SQL, so it passes SQL queries directly to your Plastic server database.
The queries can be done on one entity or several at the same time, the entities supported are any repository object such as items, branches, revisions, labels and changesets.

Have a look at this example of a complex query:

cm query
"SELECT BR1.NAME, R1.ITEMID as ITEMPATH
from REVISIONS R1, REVISIONS R2, BRANCHES BR1, BRANCHES BR2, LINKEDOBJECTS LO, LINKS L
where LO.SOURCEOBJECTID = R1.OBJECTID
and R1.BRANCHID = BR1.OBJECTID
and LO.DESTINATIONOBJECTID = R2.OBJECTID
and L.OBJECTID = LO.LINKIDand R2.BRANCHID = BR2.OBJECTID AND BR2.Name='main' AND L.NAME='merge' AND R1.ITEMID=SolvePath(c:\workspace)"
--solvePath=ITEMPATH

The result would be as follows:
NAME ITEMPATH
scm0205 c:\workspace
scm0831 c:\workspace
SCM0562 c:\workspace
SCM1371 c:\workspace
scm1755 c:\workspace


Example of a query: branches created by a certain user:




The other new feature we have included is actually an improvement on parallel development using a single branch.
Plastic support different development patterns, being “branch per task” our advised method, but if you want to work in a single branch you will enjoy this:

Every developer works from the last revision in main, if two developers check out the last revision, when the first developer checks in there is no problem, his changes are included as a new revision. But what happens when the second developer wants to check in his changes? As there as a newer revision than the one on which he was working Plastic used to advise that a merge was needed.
Now when this second developer checks in Plastic will automatically update his workspace and show a merge dialog; the result would be a new revision included changes implemented by both developers.
This improvement is not only available from Plastic GUI but also from Plastic integration with Visual Studio, so you will be faster and more productive!

Hope you enjoy our new release!

mdepedro

0 comentarios:

Subscribe to: Post Comments (Atom)