> Humm so what's the interest to use bzr and vcs-import ?
* Migration to bzr.
* Downstream (packagers) can use version control for their changes while getting automatic fine-grained updates from upstream.
* External contributors (w/o commit access) can use version control for features in development they will eventually submit through the traditional channels, like posting a patch on a mailing list.
> Do you plan to solve that soon
No. That can be solved, as the bzr-svn plugin demonstrates, but this is difficult and has a tension with the specific requirements of Launchpad imports.
> or i have just to discourage contributors to use bazaar branchs ?
This is an unrelated question.
Some people can use launchpad imports, other can use tailor, or bzr-svn, or even the upstream version control system. It is your call whether the service offered by Launchpad is adequate for your community, but it's a different problem than whether bzr is adequate for your community.
> Humm so what's the interest to use bzr and vcs-import ?
* Migration to bzr.
* Downstream (packagers) can use version control for their changes while getting automatic fine-grained updates from upstream.
* External contributors (w/o commit access) can use version control for features in development they will eventually submit through the traditional channels, like posting a patch on a mailing list.
> Do you plan to solve that soon
No. That can be solved, as the bzr-svn plugin demonstrates, but this is difficult and has a tension with the specific requirements of Launchpad imports.
> or i have just to discourage contributors to use bazaar branchs ?
This is an unrelated question.
Some people can use launchpad imports, other can use tailor, or bzr-svn, or even the upstream version control system. It is your call whether the service offered by Launchpad is adequate for your community, but it's a different problem than whether bzr is adequate for your community.
Regard.