Hello, > I also suggest dropping the test reports for the z3c.* packages: they > have been broken since the day they were added, AFAICT, which is a > strong signal that they are not being maintained. > > The point of the daily reports is to *keep the board green*, so that > when a new failure shows up, we *feel* motivated to fix it. Cluttering > the report with repeated-and-apparently-never-gonna-fix failures is > demotivating, which is the opposite of the effect we intend.
They were *definitely* green before lxml 2.3 got released. I think Marius worked on getting them green. I don't think those problems are "repeated-and-apparently-never-gonna-fix", because it's a matter of having lxml eggs/exe for all windows/python platforms. That is going to be a *blocker* for ZTK too sooner or later, because allmost all windows users are *not* able to compile. The fix right now seems to be to push Sidnei to do the releases. -- Best regards, Adam GROSZER -- Quote of the day: Do not make friends who are comfortable to be with. Make friends who will force you to lever yourself up. - Thomas J. Watson, Sr. _______________________________________________ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
