bzr-windows team mailing list archive

[John Arbash Meinel <john@xxxxxxxxxxxxxxxxx>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Sidnei da Silva wrote:
> On Thu, Oct 22, 2009 at 10:58 AM, Alexander Belchenko <bialix@xxxxxxx> wrote:
>> I've just checked svn main site and it claims that svn 1.6.6 is already out.
>>
>> The problem is two-fold. If somebody upgraded TortoiseSVN on his machine and
>> checkout then bzr (-svn) unable to work with such working copy.
> 
> Indeed. It's a though decision to make. I would personally be inclined
> to ship with 1.6.
> 
> -- Sidnei

So the reason is 2-fold.

1) As Sidnei said, we don't want to be the rude program that forcibly
upgrades an svn checkout that we aren't even supposed to be touching.
(Consider if TortoiseBzr is running, and they browse to an SVN folder
which they *want* to be handled by TortoiseSVN 1.5)

2) I'm lazy. To ship with 1.6 means figuring out how the buildout rules
need to change, what libs now need to be downloaded, and then deal with
the fallout to the build process. (I don't think I've had a release
*yet* that didn't require at least 1 rebuild of 'setup.exe'.)

If someone wants to do the legwork of figuring out how to bundle 1.6 w/
the installer, I'll be happy to incorporate that into the 2.1 series.
Probably starting at 2.1.0b2, but if it is critical, 2.1.0b1 would work.

John
=:->

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkrgYvQACgkQJdeBCYSNAANa/wCgvD2nEJ7JTyiLYxyhSd/lYNa8
S2UAmgKxtycPrqExH7Dty+e6lSQic5GX
=jued
-----END PGP SIGNATURE-----