[Zope-Coders] binary releases

[Martijn Faassen]

Matthew T. Kromer wrote:
> On Thursday, November 1, 2001, at 05:20 PM, Martijn Faassen wrote:
[snip]
> Usual either Brian Lloyd or I create the windows binary releases.  It's 
> actually fairly straightforward; it just requires Visual C++ 6.0 to 
> build; there's a script that does most of the heavy lifting.  After we 
> make the binary objects, they get put into a special internal CVS tree 
> keeping the binaries; the release builder script uses that to crank out 
> a release.
> A final step is taking the output of the release builder and running it 
> through the WISE packaging engine to create the installer.
> 
> However, I don't think we'd contemplated the notion of having another 
> 2.3 release (for Python 1.5.2) since 2.4 is the current stable release 
> branch.

PasredXML is an external package, so doesn't fit in the main release
branches. I do need to make a binary release for it though. The
only thing that needs to be compiled is Expat. ParsedXML is in the
Zope CVS though, at Products/ParsedXML.

> Having said that, what are YOUR requirements, exactly w.r.t doing a new 
> release?  Do you want a 2.3.X public release, or do you just want to get 
> your hands on a windows installer file which contains your fixes?  I can 
> make arguments either way, e.g. if we go through the hassle of building 
> another release, everyone should be able to share BUT we want to put 
> people on the Python 2.1 path and not continue to develop on the 1.5.2 
> path.

I don't want a Zope 2.3.X release at all. I do want to release ParsedXML *for*
Zope 2.3. Well, *I* actually argued against doing any such release and
releasing for Zope 2.4/Python 2.1 only, but others convinced me 
doing one last release (or perhaps two if there are minor bugs) for Python
1.5.2 would be worth it..

Regards,

Martijn