Change branch details: +junk invalid project

Reassigning to launchpad-bazaar.

I agree this is confusing, but this is correct. There is no "+junk" project, this is a special name used in branches that are associated to no project.

One solution would be special-casing +junk to be equivalent to empty. I am not convinced it would be good to reinforce the illusion that +junk is a project name.

Another solution would be a checkbox or radio button in the UI for "no project".

Yet another solution would be special casing the form validation to display an informative error message when +junk is used as a project name. For example: "+junk is not a project, it is a special name used for branches that are associated to no project. To associate a branch to no project, leave the project field empty."

Just not sure what would be best user interface.

Thinking it through, I believe the best user interface would be the special-cased error message.

If it's not obvious that leaving the project field empty has a special meaning, I suggest using radio buttons.

Project: (*) None ( ) [____________]

Thank you for the suggestion, Matthew.

As discussed with Tim on IRC previously, I think we should not add visible widgets to set a branch's project to none.

The most common case by far, and the one we want to encourage, is for a branch to be associated to a project. User interface elements should have visibility proportional to how frequently they are used. This radio-button interface would advertise too much the ability not to associate a branch to any project. I like the custom error message solution because it is invisible until the user actively tries to clear the project association.

If you have a strong opinion that we should use radio-button, I will defer to your judgement.

I don't think this is very important.

This feature was removed, but bug 402915 tracks our hope to restore a feature that is safe to use.