Cannot set branch associated to a product series

 Two use cases:

 * Martin is the author of bzr which always used bzr for its own version control. The ProductSeries.branch was never set by Importd and needs to be set to the existing mainline branch registered in Launchpad.
 * Michael maintains gnome-app-installer which was previously hosted on CVS but is now developed using bzr. The ProductSeries.branch is set to the RCS import branch but must be set to the native bzr branch.

Actually, Michael's use case is complicated by the fact that Importd is in transition and that the association between the productseries and the RCS import branch will be created after he manually set the ProductSeries.branch.

Generally, it's not clear what Impord should do when publishing a RCS import branch if the ProductSeries.branch is already set.

I think the proper fix would involve moving RCS import things out of ProductSeries and into a new RcsImport table. The association with other tables is not clear yet, I tried writing them down here but that turned complicated enough to suggest something was wrong.

That would allow doing RCS imports without imposing an association to a ProductSeries.

Some new interesting developments.

Setting ProductSeries.branch will cause the productseries page to oops: OOPS-44A491.

Michael actually requested to keep the RCS import running and have it published, but make it no longer part of the "main branch". He was actually meaning "main productseries". I interpret that as a direct request to separate the rcs import from the productseries.

Also, daf asked me if "cannot set branch associated to a productseries" means the "the UI doesn't support it" or "it's a permission problem".

The answer is "the UI does not support it".

Rejecting launchpad bug report. The canonical bug report is now launchpad-bazaar. I did not realise that you can move bug reports across products.

Discussed this issue with Robert in Vilnius, and he verbally accepted writing a specification to nail down all the desired transitions and undesired failure modes. In short, there are three valid states for a product series: no branch, native bzr, vcs import set.

Discussion about how to fix that is in progress on the launchpad mailing list.

Assigning to me, based on discussion at the last Launchpad/Bazaar meeting.

A fix is in the review queue now. The branch separates out the idea of the "VCS import branch for this product series" from "the branch for this product series".

The VCS imports system is responsible for the former while the product owner is responsible for the latter. If the branch for the product series has not been set, then the UI displays the VCS imports branch as the series branch.

Fix merged as r4028

We should be able to test it out on https://staging.launchpad.net in a few days.

This change was included in today's rollout.