vcs import details are not distinguished from informational vcs details

[Stuart Bishop]

Initial bug report from:
> Python trunk reporting SVN repository as a file:// URL
>
> The SVN URL on https://launchpad.net/products/python/trunk appears to be incorrect.

UPDATE: the Python import is now syncing from the python.org svn, so the reported problem is no longer apparent. However the underlying problem is still there.

The source of the confusion is that vcs-imports details are input for the automated import system. The purpose, scope, and occasionally, value of this data is different from the informational vcs details people often want to register in Launchpad (tags, branches, duplicate details, etc.).

There should be an obvious distinction between vcs details in the registry, and vcs details for import.

Related to bug 2649 and bug 95180.

[James Henstridge (jamesh)]

Stuart: I believe David has been testing the Python import against a local copy of the Python repository. So the value is correct for the purpose of vcs-imports.

[David Allouche (ddaa)]

James is correct. I'm testing the import using a local copy of the repository to help performance.

Actually, I am starting to believe that this mixing up of "series details" and "vcs import details" is really confusing and harmful. We should really move the vcs imports stuff into an obviously separate UI. Then, there could be the "informational only" vcs details in product series, and the "imports only" vcs details.

Matthew, what do you think?

[Matthew Paul Thomas (mpt)]

I don't know enough about RCS use to have a useful opinion. Maybe we can discuss this at the Allhands.

[David Allouche (ddaa)]

Fixing this bug is a prerequisite for fixing bug 2649. Raising the importance of this bug to High.

[Tim Penhey (thumper)]

Some refactoring of the data model is needed, and will separate the configuration for import branches from product series

[David Allouche (ddaa)]

Lowering importance to medium because it will require major database schema changes.

[David Allouche (ddaa)]

Unassigning as it will be fixed by the new code-import system.

[Jonathan Lange (jml)]

I think this should be considered fixed due to the new import system. Michael, can you please confirm?

[Michael Hudson-Doyle (mwhudson)]

Well, we've killed off the idea of structured information vcs details for now, so yes, this is dead.