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

[Alexander Belchenko]

John Arbash Meinel пишет:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> 
> ....
> 
>>> Note that I do *not* have 2.1.0b1 built yet. But the expected changes are:
>>>   bzr		2.0.0 => 2.1.0b1
>>>   bzrtools 	2.0.0 => 2.1.0b1
>>>   qbzr 		0.14.2 => 0.15
>>>   bzr-svn 	1.0.0 => something compatible with 2.1.0b1
>>>   subvertpy 	0.6.9 => 0.7.? (0.7.0 fails to build)
>>>   tortoisebzr 	no change (0.3.0, 0.3.1 needs updated bzr)
>>>   bzr-explorer 	=> 0.8.3
>>>   bzr-rewrite 	no change (0.5.4)
>>>
>>> The 2 main blockers are:
>>>   1) Needing a newer bzr-svn and subvertpy
>>>   2) Out of steam for fighting with issues (thus not even attempting
>>>      until (1) is solved.)
>> So I really think we need to change our process in a few ways to restore
>> some sort of Release Manager sanity here:
>>
>> 1. patches which change the minimum API in bzrlib need to be announced
>>    WHEN THEY LAND so plugin developers have time to respond
>>
>> 2. Plugin developers should become repsonsible for tweaking the version
>>    number released in the Windows installer.
>>
>> Would that help, assuming we have 2 branches for bzr-windows-installers,
>> one for 2.0.x and another for 2.1.0betaX?
>>
>> Ian C.
>>
> 
> Well, we should only have this primary struggle on the first release.
> Namely, api_minimum_version is now 2.1.0, and we won't have 2.1.1 or
> 2.2.* for another 6 months or so.
> 
> It was just about as painful that 4 plugins wanted to release updated
> versions for 2.0.1. Now, some things should settle down. Like Jelmer did
> the right think and updated bzr-windows-installer for subvertpy 0.7.0,
> however that shouldn't have gone into the 2.0.1 release, and it turned
> out that it broke the build anyway. (Changed a search path, etc.)

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.

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.