On Nov 9, 2005, at 10:23 AM, David W. Van Couvering wrote:
I also don't think a release manager should be *required* to run compatibility tests for JCC (although most probably will). If a particular release manager for a particular release doesn't care, it seems they shouldn't have to.
I don't think a release manager is required to run any tests, period. A responsible release manager will surely run some testing to make sure that they're not putting forward a broken build, but even that is not a requirement. Testing is done by the community, and the feedback from their testing is the basis for their plus or minus vote for the release. It is up to the members of the community interested in compatibility testing to provide those results for any proposed release. There is too much testing for a release manager to do all of it, so the community distributes the load, and voting provides the feedback mechanism.
That said, I suspect those committers who do care will probably run JCC compatibility tests and vote -1 on a release *if* JCC doesn't work because the currently implementation of Derby is not compliant with the DRDA spec.
Replace 'committers' with 'contributors', and this line of reasoning applies to all testing done w/r/t a release, not just JCC-related testing.
andrew
