[Zope-Coders] Zope tests: 5 OK, 1 Failed

2005-05-13 Thread Zope tests summarizer
Summary of messages to the zope-tests list. Period Thu May 12 11:01:02 2005 UTC to Fri May 13 11:01:02 2005 UTC. There were 6 messages: 6 from Zope Unit Tests. Test failures - Subject: FAILED (failures=1) : Zope-trunk Python-2.3.5 : Linux From: Zope Unit Tests Date: Thu May 12 22:46:

Re: [Zope-Coders] Re: ZConfig in SVN repository

2005-05-13 Thread Andreas Jung
--On Donnerstag, 12. Mai 2005 12:53 Uhr -0400 Tim Peters <[EMAIL PROTECTED]> wrote: > @Jim: what's your opinion on this subject? Jim likes copies better than externals. If you can get him to explain why, you should win a fabulous prize . But, regardless, you and Brian (I think) are in charge o

Re: [Zope-Coders] Re: ZConfig in SVN repository

2005-05-13 Thread Tim Peters
[Andreas Jung] > ... > So for Zope 2.8 this means to me: > > - the ZConfig and zdaemon should have a minimal release management > (means stable released should be tagged properly) Definitely needed. > - ZODB development can be done against any version > > - ZODB releases should done against a de

Re: [Zope-Coders] Re: ZConfig in SVN repository

2005-05-13 Thread Andreas Jung
--On Freitag, 13. Mai 2005 9:07 Uhr -0400 Tim Peters <[EMAIL PROTECTED]> wrote: - the ZConfig and zdaemon should have a minimal release management (means stable released should be tagged properly) Definitely needed. So let's do it. Amen. Tagging a package should not be so much overhead for the

Re: [Zope-Coders] Re: ZConfig in SVN repository

2005-05-13 Thread Tim Peters
[Tim Peters] >> The first time ZConfig and zdaemon get tagged, it's >> important that whoever do that first search all >> clients (ZODB and both Zopes) for changes to those >> checked in from a wrong project, and do merges back >> to ZConfig and zdaemon (I explained that dance last >> time) -- else