plastic scm 4 dvcs value proposition

@plasticscm www.plasticscm.com

Software Control Management

Francisco MonteverdeCEO Codice [email protected]

Pablo Santos President & Co-Founder

[email protected]

See a video presentation at www.plasticscm.com/launch

mailto:[email protected]


http://www.plasticscm.com/launch


Agenda Introduction to Plastic SCM • Francisco Monteverde – CEO Codice

Sofware• Company and Product Offering


Codice SoftwareCompany Background

• Founded: 2005• Product: Plastic SCM• Our Customers: from small (+5 developers) to

large developer (100’s) teams• Investors (VC): Bullnet Capital• HQ: Valladolid (Spain) & Office in Silicon Valley• Distribution: Korea, Scandinavia


Problems of yesterday’s SCMs

Tech1. Broken Builds: because

everyone is working in the main

line

2. Branching Limitations: prevent

embrace agile methods and true

parallel development

3. Arcane Branching Patterns:

Lock teams (SVN, Perforce)

4. Can’t work distributed

5. Not flexible release cycle

Business1. Long dev. cycles: high cost,

lose opportunities

2. Unstable releases – too

many bugs – poor quality – hit

the market late

3. Difficult Cooperation:

among heterogeneous or de-

located teams and offices

They are ALL solved by Plastic SCM !


The best Distributed Version Control Systems

(DVCS) supporting task driven development

for teams of any size delivering a Branching

and Merging that simply works.

Plastic SCMBranching and Merging is GOOD!

“Codice provides a solid platform that supports DVCS and provides a strong set of tools for managing the source tree that is lacking in open-source solutions”Gartner Cool Vendors in Application Development -Apr. 2011

The Coolness that is Plastic SCM (MSDN Blog reference, Dec 5th 2011)http://blogs.msdn.com/b/saveenr/archive/2011/12/03/the-coolness-that-is-plastic-scm.aspx

http://blogs.msdn.com/b/saveenr/archive/2011/12/03/the-coolness-that-is-plastic-scm.aspx



Plastic SCM 4.0

It works the way you want!

1.Fully Distributed or Centralized

repositories

2.Branching and Merging made Simple

3.Powerful GUI or straight CLI

4.Reliable & Scalable Repositories Storage

with the RDBMS of your choice


Branching and Merging made SimpleAllowing Parallel Devlopment

• Plastic SCM excels in the “branch per task” pattern

• Each task on the team’s issue tracker becomes an independent “feature branch”

• The gap between PM and development is closed

• Developers boost productivity with better isolation

• Releases are more controlled and stable than ever• The branch becomes the “unit of change” instead of the “changeset”

introducing a much stronger way to track history (of course, changesets are still available)

• The entire process is traceable through the branch explorer


Fully Distributed or Centralized reposMultisite support - DVCS

• Making distant teams work together• Full DVCS for mobile developers

Plastic SCMserver 01

Location 1

developer

developer

developer

developer

Plastic SCMserver 02

Location 2

developer

http://www.plasticscm.com/features/distributed-version-control.aspx

http://www.plasticscm.com/features/distributed-version-control.aspx


Powerful GUI: Branching, Merging and Distribution Views


Plastic SCM top features…1. Simple Branching and Merging that

works2. Fully Distributed: the only enterprise

SCM, but also can work centralized3. Powerful GUI , but also a full CLI4. Standard Repo’s: using popular

RDBMS, taking their advantages out of the box

5. Secure: ACL Based (Access Control Lists)6. Parallell Development: branch per task workflow7. Simple: easy to install, use & manage 8. Flexible: customizable, agile..9. Commercially Supported


Licensing Model Subscription and Perpetual Licenses on a per developer basis

Plastic SCM is FREE for 15 developers or less


Providing value to different roles…

For developers who love the freedom of distributed and simple branching and merging

For managers who need to lead distributed teams and understand the status of the project

For release builders who need to create stable releases


Some Customers worldwide


Codice Software Core Values

1. Proven Technology: a) Leading DVCS implementation b) 6 years development c) Key Enterprise references

2. Customer Focused: a) Flexible in response to customer feature or improvement demands b) Professional support and quick turn around c) Assistance in your deployment and to transform your development

cycle.

3. Strive for Excellence: Professional and passionate team fully dedicated to make the best

DVCS for you.


Francisco MonteverdeCEO Codice [email protected]

#plasticscm4 www.plasticscm.com



APPENDIX: EXTRA SLIDES


Plastic SCM - Gartner

November 2010 Gartner report on Software Change and Configuration Management, “Clients seeking higher performance and more-sophisticated release handling will want to consider tools like Perforce Software, AccuRev or Plastic SCM.”


What we read about Plastic SCM and DVCS

• Internet Blogs:– http://blogs.msdn.com/b/saveenr/archive/2011/12/03/the-coolness-t

hat-is-plastic-scm.aspx– http://blog.aggregatedintelligence.com/2011/12/plasticscmfirst-encou

nters.html– http://www.dzone.com/links/plasticscmfirst_encounters.html– http://stackoverflow.com/questions/8860099/using-plastic-scm-for-sm

all-personal-projects/8869600#8869600

• Latest in the press:– Plastic SCM news: http://www.plasticscm.com/company/news.aspx– Feb 2012: Sofware Development Times (SD Times, USA) B

• Branching and Merging: The heard of Version Control– By David Rubinstein http://bit.ly/x8SGg9

– Dirigentes Digital Dic 2011: http://www.dirigentesdigital.com/articulo/tecnologia/201696/monteverde/francisco/codice/software.html



http://blog.aggregatedintelligence.com/2011/12/plasticscmfirst-encounters.html

http://blog.aggregatedintelligence.com/2011/12/plasticscmfirst-encounters.html

http://www.dzone.com/links/plasticscmfirst_encounters.html

http://stackoverflow.com/questions/8860099/using-plastic-scm-for-small-personal-projects/8869600

http://stackoverflow.com/questions/8860099/using-plastic-scm-for-small-personal-projects/8869600

http://www.plasticscm.com/company/news.aspx

http://bit.ly/x8SGg9

http://www.dirigentesdigital.com/articulo/tecnologia/201696/monteverde/francisco/codice/software.html

http://www.dirigentesdigital.com/articulo/tecnologia/201696/monteverde/francisco/codice/software.html


Plastic SCM against competitive offeringsProduct

ClearCase Consistently surpassed by Plastic including much better pricing

AccuRev Lacks distributed support. Lacks good enough branching

Subversion No distributed, weak scalability, lack of strong branching and merging

Perforce Can’t go distributed. Weaker merging (renaming support)

Git No enterprise oriented, lack of ACL support, issues dealing with big files, no binary files support, no GUI, no commercial support, can’t do centralized

CVS Outdated. Issues with branching and merging, distributed, relies on database locking, performance issues

MS SourceSafe Several ages behind. No distributed, no branching, no merging, stability issues, scalability problems

MS Team Foundation Server

No distributed, lack of strong enough branching and merging. Relies on outdated tech for merge tracking


Plastic SCM vs. CVSCVS is a legacy SCM CVS (Concurrent Versions System, a.k.a. Concurrent Versioning

System) initial release dates back from 1990, which makes it one of the oldest version control systems around. CVS is still a widely used SCM both in the Open Source world and the enterprise. CVS was discontinued in 2008.

CVS limitations impact team productivity and do not allow or detect very common development operations

• Lack of atomic operations• Lack of support for moving and renaming operations• Expensive branch operations and lack of merge tracking• Performance issues due to extensive locking (when a label or a

branch is created the entire repository is locked until the operation finishes, which has a big impact considering that the operation is not specially fast)

Plastic SCM was designed 2 decades after

Comparing CVS against Plastic SCM is not fair since Plastic SCM has being designed and developed almost two decades after, using much newer technology and evolved SCM concepts.


Plastic SCM is beyond DVCS…“Distributed systems have their drawbacks as well”, according to Perforce’s Randy DeFauw and others…

• it has a steep learning curve.There is no effective GUI yet, so it appeals more to power users than enterprise developers.

• It requires a full copy of a repository to be uploaded outside the firewall to multiple disparate developers, has issues around security, and access has become more critical (although submodules are either here or on the way in several DVCS systems).

• The system is only designed to work with text-based files, such as source code.

• There is no “master” file or canonical source.

… but none of them are in Plastic SCM…

• Git has a steep learning curve -> Plastic SCM doesn't, it’s grahical and very intuitive.

• No effective GUI -> Plastic has one• Full copy of the repo -> plastic doesn't

require it• Only designed to work with text based

files -> plastic isn't restricted to this• No master file -> in Plastic SCM you may

have more than one repository but still know which one is the master copy. Unable to do a replica doesn’t mean you’re better organized (SVN, Perforce), it only means you’re unable to do distributed work

"Agile development is a big driver behind DVCS and the need for better branching and merging, the experts agreed.“ (SD Times)

Source : SD Times Feb 2012 http://sdt.bz/36328

http://sdt.bz/36328

http://sdt.bz/36328

plastic scm 4 dvcs value proposition

Technology

plastic scm gartnernovember

plastic scm news

plastic scmbranching

developer developer

developer basisplastic

encoun http

p http

distributed teams