bzr-eclipse team mailing list archive

[Piotr Piastucki <piastucki@xxxxxxxxx>]

Hi,


On 09/21/2013 09:53 PM, Alexander Taler wrote:
> Good job Piotr, sorry I've been silent lately.  I've got some
> Java work to do now, so I'll grab the new plugin and exercise it,
> and verify what I can of the bugs.
Welcome back :)
> For version numbering, I'd rather have a different solution than
> odd & even which always feels hacky to me.  What does Eclipse do
> if you substitute a different character for that final '.',
> e.g. 1.3.0+12345, or 1.3.0-12345
Maybe we should stick to what Eclipse itself and other "official"
plugins do then:
1) Keep the same version number format (with timestamp at the end) for
all builds.
2) Additionally, we can append "-r" at the end to denote a release e.g.
if a development build is promoted to release
I like this approach.
> Finally, for lightweight checkout.  I think it's crucial that we
> provide something easy and usable which doesn't require copying
> the repository.  We should either support lightweight checkout
> for local branches only (file:// scheme) or we need an integrated
> way to create and use shared repositories.
I disagree. My goal is to get rid of lightweight checkouts completely
because there are far too many bugs in bzr itself affecting them. Even
"bzr info" crashes when executed for lightweight checkouts. And since
the development of bzr is stagnant these days I do not expect any
improvement in the lightweight checkout support.
IMHO, introduction of lightweight checkouts to bzr was a mistake, they
have absolutely nothing in common with a DVCS and look like an ugly and
unfinished hack that make both the design and the implementation overly
complex. Instead of trying to satisfy every possible use case they
should have chosen the Linux way - do one thing but do it well :) E.g.
git has only 2 remote calls - fetch and push !
As I mentioned before I tried to provide an automated and easy way of
migrating from LCs to heavyweight checkouts but due to even more bugs in
bzr (bzr reconfigure) it turned out to be impossible :(

Let's ask the users to migrate their LCs to normal checkouts or branches
as soon as possible and avoid further issues with this flawed concept in
the future. I do not know exactly how many people use lightweight
checkouts in bzr and how many of them use Eclipse at the same time, but
it looks like a very weird combination and chances are there are only a
few of them. Adding any sophisticated handling of lightweight checkouts
looks like a waste of time to me.

And at the same time there are millions of git users who do not complain
about not having lightweight checkouts at all.

BTW, bzr-eclipse has been downloaded almost 800 times since we released
1.2 in June. For some statistics see the attached image.

Cheers,
Piotr

Attachment: bzreclipse_piwik.png
Description: PNG image