What's still needed to build the Windows 2.0.1 installers?

[John Arbash Meinel]

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


...

> About plugins updates...
> 
> Although I understand and feel your pain (if you remember I've built
> windows installers till May 2008) and *highly* appreciate all your
> efforts but I feel a bit sad that plugins updates makes your work harder.
> 
> But in my understanding there is not too much sense to release 2.0.1
> with fixes *only* to bzr core.

Sure. I think including updates to plugins is ok. The bigger headache is
all the plugins that think they want to stay in lockstep (by checking
api_minimum_version, etc), but then *don't* release an updated version.
Right now 2.1.0b1 is broken because it needs a newer bzr-rewrite. I
haven't been able to get ahold of Jelmer for this, and I expect it is as
simple as "no, you really do support 2.1.0" in the __init__ script.


> 
> I'd like to help to split dependecies and py2exe out of bzr.dev's
> setup.py because it really should live separate. And I said about this
> thing when Mark Hammond started to bundle TortoiseBzr to main installer.
> But nobody say something in the past and today. At least my initiative
> to use scmproj was silently buried. Today maybe this makes no sense
> because of zc.buildout do most of the work.

Well, I asked for the same thing. IIRC Mark wasn't very happy to do it,
and it fell down to "I'd rather have something than nothing."

If you want to work on it, I would really like to help where I can. I
seem to remember a couple of things you wanted me to review before you
start on anything. Can you refresh my memory?

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

iEYEARECAAYFAkrgZv4ACgkQJdeBCYSNAAPvGQCeJ520COOCoIEsc2v2H8ZwQhNT
EXsAnjWOJIFThdA21dw9s48PCpoLBKHI
=OrWP
-----END PGP SIGNATURE-----