Currently this is low-priority for Zope Corporation while we dig out of customer work, but will likely become higher priority very soon a we have at least one customer moving towards 2.7. In the meantime, it's a "volunteer effort".

Okey doke, that tells me Plone 1.1 will probably get there first then :)

If you're willing and able to collaborate on installer stuff, please let me know, as I have already automated a buildout and packaging process for Zope 2.7+ both for RPM-based systems and for Windows via Innosetup. I can check the Windows stuff into a public repository if you're interested.

I've already got an automated setup for Plone and I had one for Zope 3 (im sure its somewhere), I was doing one for Zope 2.7. Partly to take the pressure of Zope Corp., I know the 2.6.x windows installer and releases is a pain - partly to do a rather fatter bigger value added installer :) -- Andy McKay http://www.agmweb.ca

...

the pressure of Zope Corp., I know the 2.6.x windows installer and releases is a pain - partly to do a rather fatter bigger value added installer :)

Well, I'd understand if you want the value to be added to Plone, but it would be nice if some of the value trickled back down into Zope at least a little bit. ;-)

Hey it is, we'll have two Windows Installers soon, plus a new controller.

So if you're interested I've checked the Windows buildout software into cvs.zope.org into Packages/WinBuilders. The buildout software included makes it much less painful to build binaries quickly.

Cool, thanks. -- Andy McKay http://www.agmweb.ca

Oh by the way my Plone code is in Installers/pwi of the Plone cvs, looks pretty similar to your iss stuff though ;)

Yep, it's very nice! I did look at it before doing the 2.7 one, but wasn't sure of its license, so I couldn't just copy it outright. ;-) Also the Plone Windows controller rocks, and I'd like to ship something like it with Zope itself. But a) I don't know it's licensing disposition (we can't ship GPL'ed code with Zope AFAIK) and b) it will need to change a lot due to the install and config changes in 2.7+. So, anyway, if there's any way we can work together on the installer or controller stuff, I'd be very happy. You know more about this shit than I do. ;-) Here's what I know still need to do: - figure out how to get event/access log rotation to work (sigusr2 definitely wont work ;-) - provide a better default config file for Windows (backslashes instead of slashes). - Log startup tracebacks when running as a service to the Windows event log. - C

Im not trying to maintain the Controller any more, mostly because I dont really enjoy trying to faff with MFC code. I've tried to get a gui controller started using wxPython a few times, but ran out of steam before I get anywhere a few times.

Ya. Me too. ;-) I was also about to write a different service controller today because pythonservice was giving me grief, then luckily I stopped myself. (FWIW, each instance can have a separate service registered for it at install now; I know that gave you problems at one point).

Either way the Controller does too much work that is now done in 2.7, I'd like it to:

- talk to the tools in bin to create new instances (it tried to do its own thing)

- talk to ZEO

- read and write the ZConfig file

Reading and writing the ZConfig file would be great (writing it will be tricky - ZConfig doesn't retain enough state currently). Not quite sure what you mean by "talk to ZEO", but I suspect you mean that you want to determine if ZEO is up or down via the controller. That'd be useful, but I suspect it might be more (and less "frameworky") to have a separate controller app for ZEO itself. Personally I'd like to see a GUI controller that got installed on a per-instance basis which had the features of the current UNIX zopectl plus the ability to install and deinstall the service for the instance. This is as opposed to a single controller for all instances on the same machine. I'd like to see instance creation happen in the domain of a separate (also GUI) application. All that said, I'd love anything GUI at this point. ;-) Firing up a DOS box for people is just so nasty.

...

So, anyway, if there's any way we can work together on the installer or controller stuff, I'd be very happy. You know more about this shit than I do. ;-)

Likewise, when, how or what - I dont know.

Yup.

Dont we use the logging module now? Can we just plug in the NTEventHandler? I haven't looked at 2.7 so guessing.

We can, but currently 2.7 startup logs to a StartupHandler which only gets flushed to "real" handlers after we "setuid" (a noop on windows, but the logic is stupidly the same now for both UNIX and Windows). This needs to be fixed. I also haven't figured out how to register an event log identifier for the Zope application (as opposed to the service control manager app; pythonservice does that for me there). As a result, the event log refuses to accept any messages from Zope when you try to use an NTEventLogHandler. Anyway, if you have any brilliant ideas or code you want to share, let me know... - C

2.7.0b2 was released yesterday with both of these bugs fixed. Is that soon enough? ;-) On Wed, 2003-08-27 at 05:42, Joachim Werner wrote:

Hi!

WRT the Zope 2.7 timeline: Couldn't we just get a new beta that includes the most critical bug fixes very soon? If 2.7 doesn't get deployed on "almost production" systems there will not be too much further testing I guess. And currently most non-experts will not even be able to get a Zope 2.7b1 system up and running with additional Products.

The main issues that come to my mind are:

- Fixing the zope.conf so you don't need to manually add a path to the Products directory

- Some simple example in zope.conf to help with ZEO setups.

- The fixes to the VirtualHostMonster, so that the tab for configuring mappings is displayed again (fixed in the CVS)

I am willing to help with that. I'll just have to get my CVS checkin SSH certificates fixed first ...

And of course we could have a Zope 2.7 bug day, too.

Cheers

Joachim

_______________________________________________ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )