Myrna van Lunteren wrote:
One of the aspects that I let weigh in on deciding to call a vote or
to hold it up for these critical issues, is that no one *has* signed
up. I can theorize based on past track records & hope that certain
people might step up to the plate, but as long as there's no firm
assignment coupled with an indication from the responsible individual
that it's going to be done within a reasonable time frame, I don't
think it makes sense to hold up a release...
One other aspect is how does a release reflect on the Apache brand and
the Derby community. The Apache Way includes:
- consistently high quality software
- security as a mandatory feature
I would encourage folks to consider all the information about the
release before voting, not just a run of the functional tests on some
platforms. That's information from comments like Bryan's (quality is
getting better), the outstanding bugs, non-functional testing reports
from others, etc.
I'm slightly worried about the value given to the functional tests
passing, because in some cases we find a bug, make the test pass by
avoiding the bug in the test and enter a Jira bug report. Thus while we
(I hope) wouldn't make a release if the functional tests are failing, it
seems we are quite happy to mask those failures by entering bugs. I
understand why it's done (to avoid others wasting time to see if they
caused those failures, ie to have clean runs), but it does devalue the
functional tests a little. Or at least one must look at them along with
the outstanding bugs.
Dan.
