ScmProj

ScmProj is a plugin for organizing set of VCS branches as united project.

Installation:

Current-user only install

 1. Create ~/.bazaar/plugins directory if not exists
 2. cd ~/.bazaar/plugins && bzr branch lp:bzr-scmproj scmproj

System-wide install

Alternatively, you can install them at the system-wide plugin location:

$ sudo ./setup.py install

Check it

You can check whether it's successfully installed by doing:

bzr plugins

and looking for 'scmproj' entry in the output.

If you want to ensure it's actually working you could run tests:

bzr selftest scmproj

What is new in this release:

• New maintenance release of scmproj 0.6.2.
• Compatible with bzr 2.5.

What is new in version 0.6.1:

• New version of scmproj 0.6.1 provides bugfixes and improvements in project v2 support.
• New features: project-add and project-branch commands.

What is new in version 0.6.0:

• This release introduced new layout for project config (in .bzrmeta/scmproj directory of top-level component of the project) and support for snapshots.

What is new in version 0.5.2:

• I think it will be the last release in 0.5 series.
• Next release will bring new format and config layout.
• Old format will be still supported for all operations except project-init command.

What is new in version 0.5.1:

• The changes in this release is mostly focused on improving project-command (pcmd), project-update and project-publish commands.
• Now it's possible to easily specify for which components you want to run your commands (with pcmd --include/--exclude/--select).
• Also I've added new (simple) feature to internal commands executor: using some checker function it's possible to check component tree for some condition and run the command only for components which conform the condition. Possible conditions are:
• all components;
• tree has changed files;
• tree has only unchanged files;
• local branch and origin branch have different tips;
• local branch and origin branch have equal tips.
• These conditions automatically used by other commands like project-commit, project-update, project-publish.
• The net effect from this small improvements is much friendlier and faster interface. Commands now prints mostly only useful info, which is important if you have more than 3-5 components.

What is new in version 0.5:

• Subprojects simplified implementation (without variants support and read-only flag).
• ``project-publish --no-strict`` can be used to invoke ``push --no-strict`` for components trees. (Bug #474799)
• ``project-command --dry-run`` will show what would be done, but don't actually do anything. It's better to use with option --verbose.
• ``project-info`` now shows the info on components and subprojects. (Bug #313166)
• ``project-command --shell`` can run shell commands for each component instead of bzr ones. (Bug #349069)
• ``project-command --varN XXX``: new command-line options ``--var1``, ``--var2`` and ``--var3`` allows user to specify additional template variables for substitution in commands templates. (Bug #489722)
• commands to work with local project now possible to invoke from subdirectory and not only from project root. (Bug #313150)
• Compatibility breaks:
• Removed support for boxed workspaces.
• No more pretend that we can suport any vcs other than bzr. Now config with VCS option set to other vcs will raise error.

What is new in version 0.4.6:

• This is bugfix release for scmproj 0.4.5.
• In the future I've decided to significantly rework scmproj plugin, so current state of its code now put into maintenance mode.

What is new in version 0.4.5:

• This plugin is poor emulation of nested trees based on ideas, design and implementation of similar features in other VCS. Scmproj has not use any code from native bzr nested trees implementation.
• I define current state of my plugin as alpha-level software. It works good enough to use it in real work, and we using it in my team at work for managing 2 complex products consisting from 3 to 10+ components. I don't say that everything going easy with it, but without such plugin my team will be unable to manage these products manually.
• My further plans is to rework scmproj based on the feedback I've got in last 6 months (better config, snapshots and subprojects), and start accommodate some code from bzr nested trees. I'm really hope to see nested trees implemented in bzr soon, but I can't wait forever and I need some non-ideal solution right now.

Requirements:

• Python