Ball: Plastic SCM

I had find many products about tool box plastic from some websites such as

	Tool Box Plastic 18" We supply full range of Tool Storage Products, sucha s Tool box, Tool case, Tool chest, Tool bag, Tool..
	pvc sheet, PEVA sheet, Table cloth.. plastic sheet, Table cloth, PVC table cloth, Table cloth sheet, Vinyl sheet for table cloth, PEVA table..

And you can see more from
covert electronic devices
fiber grade masterbatches
property security devices
high polymer polyethylene
plastic products recycled
equipment and instruments
calcium carbonet granules
hish density polyethylene
infrared magnetic devices

Plastic SCM snapshot.

Plastic SCM is a commercial SCM system developed by Codice Software. Plastic tries to focus on parallel development, branching and merging and security.

Contents

1 Features

1.1 Branching support

1.2 Smart branches

1.3 Branch explorer

1.4 3D Version trees

1.5 Directory versioning

1.6 Merge tracking

1.7 Diff and merge tools

1.8 ACL based security

1.9 Customizable database backend

1.10 Configurable workspaces

2 Releases

3 External references

4 References

//

Features

Branching support

To enable parallel development Plastic focuses on branching. The main difference between the Plastic branching model and the ones implemented by systems like CVS, Perforce or Team Foundation Server is that instead of copying everything (or just the metadata) to the new branch, branches are created as empty objects. Only when an item is modified, the newly created revision is placed on the branch. Subversion implements branching by appearing to make copies of the entire branch, but deferring the actual copying until the file is changed ( la copy-on-write).

So a branch only contains files or directories modified from its parent branch.

This approach makes easier creating lots of branches, allowing the implementation of branching patterns like "branch per task", detail in the book SCM Patterns[1] and at CM Crossroads[2].

Plastic branching model can be compared to Clearcase (both UCM and base).

Due to its underlying branching model Plastic can handle thousands of branches in a single repository with no hassle.

Smart branches

Plastic 2.5 (July 2008) introduces smart branches.

Smart branches are like regular branches but the user can define their branch inheritance.

It is important to note that a branch in Plastic is just a new object in the system. It is empty upon creation, but it virtually contains the files and directories of it ancestor (or ancestors if a multi-level hierarchy is created).

A smart branch can be created from a specific label or tag, a changeset or a specific branch.

Inheritance from a label: all the branch content comes from the label, but if a modification is done, the change goes to the branch. It is a good option to implement a bug fix against a well-known starting point.

Changeset: the smart branch initially contains the files and directories at the changeset (not modified at the changeset, but the status of the parent branch at this changeset).

Last from a branch: this is dynamic inheritance. The branch takes all the LAST revisions from the parent branch, and if something changes on the parent, the changes are propagated into the branch. Modifications on the branch itself are loaded before the ancestors.

Branch hierarchies can be tuned using the graphical user interface. Multiple levels of inheritance can be set at any time.

Branch explorer

The branch explorer is a user interface which draws all the branches on a repository. It also draws the merge relationships between branches and the inheritance links.

The branch explorer was initially introduced on Plastic 1.5 and has been improved since then. In 2.0 it introduced interactive support so common branch operations like creating a new branch, merging and running common queries can be performed from the explorer itself.

The explorer draws:

branches

merge links

parent links (inheritance)

changesets (squares on branches)

labels and tags

Changes on branches or changesets can be inspected from the explorer

3D Version trees

Plastic provides ways to visualize version trees for both files and directories. The 3D version tree shows the evolution of a given file or directory, including merge links (the green arrows). Labels and extended information are also included.

More recently new links have been introduced to support:

Regular merges (the green ones)

Interval merges (cherry picks): both the interval and the merge are drawn

Subtractive merges

Revert operations

Directory versioning

Plastic supports directory versioning. Full renaming and moving are also supported.

Merge tracking

Each time a merge is performed, a link is created between the source and destination revisions. The link is not only important to visualize the process (to be displayed on a version tree), but used internally by Plastic in the following merge operations.

When you merge a branch, merge links are created, so if you try the merge again, Plastic notices there are no merges left.

Diff and merge tools

Text differences

Image differences

Text merge

Plastic includes the following tools:

Code differences: code file differences with syntax...(and so on)