bzr-eclipse team mailing list archive

[Alexander Taler <dissent@xxxxxxxx>]

> I am not sure if I was clear enough about LCs in my last email, so let

You were pretty clear :)

I agree with not supporting a feature if it's broken, and I
understand why Eclipse would excarcebate the problem.

But I think there's value in not copying the entire repository
for every branching operation.  This is one reason to prefer
Bazaar over Git.  Therefore I would like to see phasing
lightweight checkouts happen at the same time as support for
shared repositories.  Shared repository setup could fit into the
project creation wizard as an advanced option selection.

> 1) ask the users to migrate LCs manually (currently I cannot see a way
> to provide an automated migration that will satisfy everyone)
> 2) provide enough information: useful links, wiki page etc.
> 3) answer any questions related to the migration
> 4) avoid introducing any kind of partial or dodgy LC support to the
> code unless it turns out to be absolutely necessary (e.g. requested by
> the majority of users)

Manual migration steps during an upgrade are a horrible user
experience.  I think we need to explore automated options for
migration a bit more; probably the simplest approach is to have a
process which converts a LW to a regular checkout, and prompt the
user to do it.  But leave the option for the user to find their
own migration solution instead.

Perhaps the first question is if there's a way to find out how
many people use LW checkouts.

Alex

-- 
idereal | deliver                       http://idereal.co.nz/
Get your software to market sooner      022 659 0282