Re: Two releases?

On Tue, Oct 9, 2012 at 6:18 AM, Yury Don <don@rosfirm.ru> wrote:
> 09.10.2012 06:21, Daniele Varrazzo пишет:
>
>> - if nobody opposes it, drop support for zope (further zope issues, if
>> any, can be dealt with in the 2.4 maint branch)
>
> I and one my collegau oppose since we use psycopg with zope (presentrly with
> zope 2.9)

Hello Yury, thank you for letting us know.

The problem with Zope, as I've said several times, is that nobody is
maintaining it. There are two bugs open in the tracker and I haven't
found anybody to show me a failing test. Even the guy who opened
ticket #123 (http://psycopg.lighthouseapp.com/projects/62710/tickets/123)
has failed to come back to help fixing it or giving me feedback I'm
going in the right direction. He has shown the log of a failing
interaction between a page and the db and not reported how to
reproduce it. ZPsycopgDA is not rocket science, but it takes knowledge
of the life cycle of a zope page, and I don't have it.

It's a matter of responsibility: Federico and me are the only people
doing maintenance on psycopg2 and none of us use Zope. The QA level on
the rest of the adapter is *very* high and on ZPsycopgDA is exactly
zero. I've fumbled several times breaking things in the past (big
times, see isolation consts), but I can fix these errors; when
somebody breaks zope nobody notices for one year and four releases.

On Zope side, none of the people I've asked for help have ever
answered, in this ML and in others. When I've asked about it to the
developers of the biggest Zope company in Italy I've been answered
"nobody uses ZPsycopgDA anymore: everybody just uses zope.sqlalchemy".

When I say I want to drop support for zope I mean I want to leave
ZPsycopgDA and psycopg2da (for zope3), which are not part of the
psycopg2 package, out of psycopg2 repository. These are two separate
directories living in our tarball and not released if not in the sdist
package. There is not even a setup.py for them: there is a package of
PyPI that somebody else I don't even know maintains
(http://pypi.python.org/pypi/ZPsycopgDA/). For me this is great: for
what I see an external project just depending on psycopg, with its
docs and tests if they want, is the best solution in term of quality
(i.e. people who care responsible for it). They would have all our
support.

In the meantime, if you can provide some help for the mentioned
outstanding zope issues, that would be great: as you can see from my
roadmap they are basically the only blocker for the release of a
bugfixing package. If we accepted to drop them we could release 2.5,
with juicy new features, *before it*, and that's not good IMO.

Thank you very much

-- Daniele