Jim Fulton wrote:
On Jul 31, 2006, at 2:02 PM, Philipp von Weitershausen wrote:
If you ask me, the slipping of the Zope 3 June release is mostly due to
the lack of a release manager. If we had a release manager who'd kick
people's asses, we might have more betas since the first one and we
might even have a final release.
I don't agree. Except for a few people, there hasn't been much interest
in fixing bugs. Releasing betas when bugs reported earlier haven't been
addressed is counter productive. Why should people bother testing if
they don't think the bugs they report are going to be fixed.
Disclaimer: I'm not involved in the Zope 3 release process, so what I
say below is completely general and not specific to any events having
gone on in the Zope 3 community.
I'll note from my observations in the Plone community that not having
someone bitching is a pretty good way to ensure things don't get done.
Everyone has a lot of projects and personal lives that get in the way. I
have several bugs assigned to me in the Plone tracker that I never seem
to get around to doing. But when Alec or Limi or someone else tells me,
we need this or else we can't ship, that makes them jump up the priority
list. Having someone vocal with authority to instill a sense of urgency
in people is a fairly important part of managing open source projects.
Zope3-dev mailing list