On 10/6/07, Jim Fulton <[EMAIL PROTECTED]> wrote: > - We need to decide what a Zope 3 release is (or maybe multiple > flavors). I favor copying the linux experiences, but have an open mind.
I'm not sure what you mean with that, but for me, a known good set, or what you call it, plus a buildout that uses this, would be enough for a Zope 3.4 release. If we easily can build the old standard downloadable tgz as well, then fine, but it's not necessary. > - We need a *realistic* (especially wrt available resources) process > for managing releases. There are 2 aspects of this. We shouldn't > make plans for which there aren't enough resources. We also > shouldn't plan significant tasks that people won't care enough to > work on. I think the classic Zope 3.4 release is a good example of a > large effort that really wouldn't benefit many people, if any. Do you have a sort explanation on what is the missing resource? Is it, as it was for 3.3, lack of people-hours with knowledge in fixing the last bugs? -- Lennart Regebro: Zope and Plone consulting. http://www.colliberty.com/ +33 661 58 14 64 _______________________________________________ Zope3-dev mailing list Zope3email@example.com Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com