Release Notes

Multi-level submodule support.

Now a full hierarchy of submodules can be added. It is possible to have repositories as follow:

default/codice
default/codice/plasticscm
default/codice/plasticscm/windowsgui
default/codice/semanticmerge

Before only 1 level of submodules was allowed, but now a full hierarchy can be created, which is useful when a certain namespace policy must be enforced.

All the submodules inside a given repository are stored inside the same database as the repository, actually using different table name prefixes or schemas in the case of SQL Server.

Remarks:

* A submodule can't be moved to a different repo. It stays on the repo where it was created.

* A submodule can be moved "inside" a different submodule and submodule hierarchies can be freely modified just applying repository rename operations. It means you can start with

default/codice
default/codice/plasticscm
default/codice/plasticscm/windowsgui

And transform the hierarchy as follows:

default/codice
default/codice/plasticscm
default/codice/windowsgui

And even rename "codice" to "plastic-code" and then:

default/plastic-code
default/plastic-code/plasticscm
default/plastic-code/windowsgui

* When you delete a submodule, you delete all the submodules inside it! Remember that delete doesn't really remove the submodule, it stays on the database and it is just unlinked from Plastic (as happens with repositories).

* A submodule inherits permissions from its parent submodule. When you move a submodule, the permissions from the new parent will be applied.

GTK/Mac GUIs: 'Open' and 'Open with...' context menu options are now available in the 'Pending changes' view.

Gluon: Usability improvements. When deleting an item from the workspace explorer, the the nearest sibling is focused (instead of the root item as it was done before).

Gluon: Usability improvements. When typing text in the comments textbox, the focus is preserved even if the 'checkin' view is being refreshed.