bzr-eclipse team mailing list archive

[Alexander Taler <alex@xxxxxxxxxxxxx>]

Sounds reasonable.  How about:

* Change new project wizard to disable lightweight checkout as an
  option for remote branches.
* Add a page to the bzr-eclipse wiki explaining the issues with
  lightweight checkout, and how to use shared repositories.
* Add a link to the new project wizard alongside lightweight
  checkout (whether it's disabled or not) to the wiki page.

Alex

  > Actually I do not think we should remove the support completely. As
  > mentioned before I would like to discourage people from using lightweight
  > checkouts rather than break their workflows. Removing the respective option
  > from the new project wizard, adding warning to known issues and possibly
  > showing a warning when a lightweight checkout is in use should do the
  > job. In case of local filesystem, we can encourage users to consider using
  > shared repo and regular checkouts instead of lightweight checkouts.

  > Cheers, Piotr

  > On Mon, Jul 15, 2013 at 11:18 AM, Alexander Taler <alex@xxxxxxxxxxxxx>
  > wrote:
  >> 
  >> The concern with removing lightweight checkouts is that it will break
  >> people's workflows.
  >> 
  >> Perhaps we should have a halfway measure where we can support lightweight
  >> checkouts of branches on the local filesystem, but not remote branches.
  >> 
  >> For the scenario of adding an already created lightweight checkout, I
  >> guess the answer is to try and detect and throw an error if it's not
  >> supported.
  >> 
  >> Alex
  >> 
  >> --
  >> idereal | deliver http://idereal.co.nz/ Get your software to market sooner
  >> 022 659 0282

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