Tarmac should allow for other branches

[Ted Gould]

Tarmac needs a way to specify a branch that isn't the development focus for a branch. Sometimes merges happen to other branches and it would be nice to use tarmac on.

[Paul Hummer (rockstar)]

So I acknowledge that this needs to be done, but right now, I'd like to get more users using what is there now. I'll fix this after some other features are implemented.

[John A Meinel (jameinel)]

Just a comment that this is something that would block Bazaar from switching to Tarmac from PQM. Namely, our release branches (bzr.1.15, bzr.1.16) are managed by PQM, and we certainly wouldn't set them as a development focus.

[dobey (dobey)]

The latest version of my linked branch should work, as long as the test command is the same for all branches of a project.

We need to also add support for per-branch configuration, rather than just per-project, so that test_command can be defined differently for different branches of a project, as there may be differences as new features are added on trunk, while stable branches don't receive much change. Should we file a new bug for this, or do the infrastructure changes necessary for it in this branch? I'm fine doing it either way, but it's going to be a fair bit of code, so I'd suggest a new bug and separate branch. What do you think Paul?

[Stefano Rivera (stefanor)]

Another confirmation that this is a major pain. Tarmac works pretty well for our trunk, but not for previously released branches that we still maintain bugfixes for.

[Paul Hummer (rockstar)]

Rodney, I just saw your comment. I must have just skipped over your comment earlier. The answer is yes: we need per-branch configuration. Tarmac 0.3 has a new config format that will do this.

Stefano, acknowledged. It's been a matter of finishing up the porting of the Tarmac 0.2 code to Tarmac 0.3. It should happen in the next few weeks.

[dobey (dobey)]

This is already handled in trunk by Paul's code.