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.

Plastic SCM Release 4.1.10.345 is out!

Monday, September 24, 2012 Amalia 0 Comments

Plastic SCM 4.1.10.345  has been released!!

In the latest releases of Plastic SCM, versions 4.1.10.339 to 1.10.343 we introduced new features and bug fixes.

Beside the full release notes here, this blogpost will highlight some of them.

Just in case you haven't downloaded this version yet, visit download page.

Features

2D Tree

Now, the Shell Extension shows the 2D tree instead the 3D revision tree.

Bugs

Changesets out of Branches

Branch Explorer shows the remote changeset for a single branch caused that the view calculated the layout incorrectly. Fixed!!

Security System

The system will show an error message if the user tries to leave the permissions of the repository server without any user or group specified, to prevent situations where there's no permissions to do anything. Fixed!!

Images Diff Tool

Now the form has a default minium size. Fixed!

GUI

Fixed alignment of Preferences and RSS Notifications icons, and some small issues in the About form.


Enjoy it!!

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.

Plastic SCM Webinars are out!

Tuesday, September 18, 2012 Amalia 0 Comments

I'm glad to announce you the official 2012 webinars calendar!
We're bring you a packed full of FREE webinars. We will be hosting one webinar every week on we will introduce the new features of the Plastic SCM and explain other best known.
Click through to take a look at the webinars that will be taking place and register for the one's that you would like to attend for FREE!!
The 4.2 release is almost here and we want to share all the new stuff with you! Join us!




2012/09/26 - Web UI with Plastic SCM 4.2

Introduction to the new product of Plastic SCM. WEB UI is the place where you can make quick consults, see the evolution of your work.
What do I need? Nothing, it's delivered as a service over Internet. It's useful and simple. We will show you all the features, how to get it and install.

When: 2012/09/26 5:00 PM – CEST

Register to Web UI Webinar


2012/10/03 - About Subtractive Merge
Is able to undo a previously introduced change?
This functionality allows you to perform a merge that will exclude changes that you made and now you want to get rid of them.

When: 2012/10/03 5:00 PM – CEST

Register to Subtractive Merge Webinar


Plastic SCM team are preparing the next webinars. Stay tuned!!


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.

Plastic SCM Release 4.1.10.343 is out!!

Friday, September 14, 2012 Amalia 0 Comments

A new release of the 4.1 version is out: Plastic SCM 4.1.10.343 has been released.

The features of each Plastic SCM release, up to and including the latest version, can be found in the release notes page.

Besides the full release notes, this blogspost will highlght some of them. Just in case you haven't downloaded this version yet you can do that here.

Bugs

Merge and conflict resolution

The structure conflict resolution can change the merge result (not only when the resolution affects to the destination). So we have recalculated the merge to ensure the merge result update to date. The merge conflict resolution has been improved in order to avoid impossible conflicts resolution combinations and reduce the number of conflicts. Fixed!


"cm query" command

The --repository option did not work outside a workspace.Fixed!

In addition to this, a bug related with the --solvepath option has been fixed.


"cm replica" command

The command was looking into the workspace repository even when non-related repositories were involved in replica. Fixed!


Visual Studio package

When you cancelled changing the current workspace in the workspace working info view, a crash happened. Fixed!

Enjoy it!!
   

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.

Plastic SCM Release 4.1.10.341 is out!

Friday, September 07, 2012 Amalia 0 Comments

Plastic SCM 4.1.10.341  has been released
The features of each Plastic SCM release, up to and including the latest version, can be found in the release notes page.
As you know we're releasing a new version weekly (in fact we produce new versions on a daily basis). This week we announce twice and the last one we made public includes a few bug fixes you might be interested in:

Bugs

Metacharacters

Now, the directory or file name that contains special chars, such as '$' or '^' can be matched with the regex system used in the cloaked.conf, ignored.conf and hidden_changes.conf files. Fixed!!


Restore the "name_conflict" names to real ones

The "path in use" situation is undone when the original path, that was in use during the merge process, is released after the merge process. Fixed!!


Replicated changeset without tree

The replica was not working correctly when a checkin operation was performed between two specific steps of the replica process, due to a concurrency issue very unlikely to happen. Fixed!



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.

Plastic SCM release 4.1.10.339 is out!!

Friday, September 07, 2012 Amalia 0 Comments

This week we have a new release: this time we're annoncing 4.1.10.339 (Build 339 as we name it internally). It is a new release of the 4.1 version, including new features!! and a number of bug fixes.
While you can read the detailed release notes,this blogpost will highlight the most relevant features and bugfixes.
Remember you can find the latest installer here.

Features

GUI 4.0: implement overlapped functionality
Implemented a mechanism to dectect new changes on the repository from the Pending Changes View. This mechanism is useful in a single branch working pattern. When multiple developers are working on the same branch, it is usual to get your workspace out-of-date because other developer checked-in some changes that could overlap your changes.
You can activate an option called "Look for newer changes in the repository" to use this feature.
When selected, the Pending Changes view calculates if there are newer changesets in your working branch; in this case,it shows an informative panel. This panel will show you the new changes in a merge panel, and you can update your workspace to the lastest changeset of your branch.
Figure 1: Pending Changes Options

Figure 2: Overlapped Information Panel

Figure 3: Overlapped Merge Information Panel

Figure 4: Overlapped Update Information Panel


Switch to branch command: add parallel option
The comand switchtobranch or stb, allows users to work in a branch. it sets the specified branch as the working branch.
The update command supports a new option, --parallel, provided with the options:
  • --parallel
  • --noparallel
By default, the option  --noparallel is used.


GUI 4.0: improving Diff View
The diff view includes this new features:
  • The date of the change (timestamp) is shown in the details, along with the timestamp for the reviewed object.
  • Now it is possible to copy the file name. Added a context menu with the option "Copy" in the file list.
  • The selected file color is more noticeable (it was not visible in some           screens, due to brightness and contrast configurations).
  • Preserved the syntax highlight preference when switching between files.
Figure 5: Diff View: date of the change

Bugs

Merge
An issue related to having a moved deleted conflict has been fixed when the move source and destination has been deleted. Some conflict raised by the "path in use" protection has been avoided. The conflict dependencies detection has been improved. Fixed!!
Shelve
When a shelve with an added structure was applied and committed, then the children were not properly stored under some special circumstances. Fixed.
GUI at 120 dpi
Fixed an aesthetic issue in the main form that was noticeable when showing the GUI at 120 dpi. In addition to this, the left panel that lists the Plastic views now preserves the size when you close and reopen the GUI. Fixed a problem with the Extended information panel and the Advanced view in the Branches view.
GUI: Sync view
Fixed an unhandled exception when cancelling a replication operation that failed from this view. The form was disposed when the user updated the GUI. Fixed it!
Xlinks
Xlinks: Some issues related with an xlink that reuse an old controlled path have been fixed. The issues related with reuse an item path for an Xlink, and vice versa, have been reviewed and fixed (update, merge, unco). Fixed!!
Enjoy it!

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.

Self documented development through inch-pebble checkins

Wednesday, September 05, 2012 Amalia 0 Comments

“Nothing can be quite so helpful as well-placed comment.” This the first sentece in the chapter 4 of Clean Code wrote by Robert C Martin.

There are good comments: when you find a weird bug or need to understand why a certain change was done, then you wish you had proper documentation. And, indeed, there are bad comments. Let explain yourself in code to avoid writing comments in bad code.

The problem seems hard to solve. Good comments can help and techniques like diff debugging and proper code review tools can help too. But what every developer does on a regular basis is checking in code to his repository. What if the way in which you check in could help self documenting the code?

Side note: I find the technique I describe here not only good for self documenting changes but also to capture the way in which lead programmers work in such a way it can be used to teach the newcomers...

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.

Mylyn: Migrate to Plastic SCM 4.0

Tuesday, September 04, 2012 Amalia 0 Comments

What is Mylyn?

Eclipse Mylyn allows you to integrate with task managers such as Bugzilla or JIRA. The idea is to pass from typical uncoordinated development to more task-oriented development, so that you can estimate a task’s duration and associate a particular context (classes, methods, attributes) with it. These contexts are,integrated with the version control system which then interacts with the development environment and issue tracking system used by the company.

Mylyn is an Eclipse plug-in whose main features allow it to:

  • Retrieve tasks: from an issue tracker system such as Bugzilla or Jira.
  • Filter context depending on current working task (context provider): It allows the developer to filter the Eclipse resources that are related with the current active task. It's very useful for large projects, when working on a task which only changes a few resources.

The main idea is improving the typical uncoordinated development. Eclipse Mylyn is integrated with the version control system and with your issue tracker. By making task context explicit, Mylyn also helps with multitasking, planning, reusing past efforts, and sharing expertise.

Installation

Mylyn requires Java 5 or later. The easiest way to get it is to download one of the packages that contains it.

To install Mylyn for your version of Eclipse, use the Eclipse Update Manager:

Help -> Software Updates -> Find and install -> Search for new features to install



Tasks

Mylyn provides support for working with two kinds of tasks:

  • Local Tasks: provide basic task management features. They are private so only the owner can see them.
  • Repository Tasks: are stored in a task repository that corresponds to an external application. It contains tasks are shared

How Plastic SCM improves the Mylyn plug-in

Depending on the active task, Plastic SCM can handle the SCM configuration that best suits the active task. There are different use cases:

The Plastic SCM Mylyn plug-in inherits the issue tracker configuration already configured on the Plastic SCM GUI client: “Task per branch” and “Task per changeset”

  • If the Plastic SCM GUI configuration states that the working mode is “Task per branch":
    • The Plastic SCM Mylyn plug-in will try to match the selected task identifier in Eclipse with a branch, and will propose that branch to switch to, before changing to the selected task context.
  • If the Plastic SCM GUI configuration states that the working mode is “Task per changeset":
    • The Plastic SCM Mylyn plug-in will link the commits created when a task is activated to the corresponding task in the issue tracker system, as the Plastic SCM GUI does. Also, the comments template will inherit the format from the Mylyn configuration (although it can be changed).

The Plastic SCM Mylyn plug-in does not inherit the SCM configuration from the Plastic SCM GUI client.

  • The Plastic SCM Mylyn plug-in will allow the user to specify a prefix for branches that can be matched with a task on the issue tracker system. No interaction with external issue tracker system is performed.

Mylyn, Plastic SCM, and JIRA

Plastic SCM offers you the possibility to bind to an issue tracker system. To install this, go to:

Plastic SCM preferences -> Issue tracking -> Bind to this issue tracking system

In our example, we are going to use JIRA as our issue tracking system.


The next figure shows you in Eclipse Preferences -> Team, all the version control systems you can choose. In our case, we selected: Plastic SCM for Mylyn.


Plastic SCM for Mylyn supports two working mode. You should select one of them:

  • Bind issues to Plastic SCM branches.
  • Bind issues to Plastic SCM changesets.

Plastic SCM branches

When you choose “Bind issues to Plastic SCM branches”, there is an option to select Branch Prefix. The next figure shows you how we selected the Plastic SCM workspace and the branches to switch to in Plastic SCM.


When the task is finished, the Plastic SCM Diff Tool View shows you the differences between versions.


Plastic SCM changesets

The other option that Plastic SCM for Mylyn supports is: Plastic SCM changesets. This next figure shows Plastic SCM checking the pending changes.


And you can verify your changeset after check-in..


Enjoy our favorite Flickr Plastic SCM -Mylyn photos!!

Remember you can find the latest installer here.


0 comentarios: