Rick Hillegas (JIRA) wrote: >I am very keen to commit this patch because several other chunks of JDBC4 work >depend on it. However, I'm also eager for this patch to be reviewed by one of >our network experts (Kathey? Bryan?). Hopefully, after all this time, the >comments will be fit and polish issues which Narayanan can address in a >follow-on submission. > > > First of all, I would like to dispel any myth of myself as a network expert. I have dabbled in DRDA but know of quite a few people who have recently submitted superior DRDA work and have quickly surpassed my meager knowledge and certainly my talents in this area. DRDA is an area, quite frankly, where my personal goals are centered around knowledge transfer and support and not future development.
Regarding the patch, I would love to review this patch, but find myself chin deep in customer bugs and other reviews at this very moment and unable to pull away to review this patch. But do ... 1) Encourage absolutely *anyone* with interest in seeing this patch going in to review it from a DRDA perspective, even if they have never ever looked at the DRDA spec before. The kind of fresh perspective we have seen on DRDA on the list from Oyvind, Bryan, Knut, Deepa, Francois, Army, Dyre, Sunitha, Tomohito, Bernt, you and others is probably what is needed here. With all that is planned to go in before April 7, a lot of other folks are going to have to learn about DRDA and review DRDA related patches too. 2) Encourage you not to compromise your instinct as committer that this patch needs a DRDA review. The job of : Lorax is everyone's job especially committers. My opinion is that DRDA is a soft and fragile quality spot with insufficient regression testing to make major enhancements with confidence that nothing will break. If we lose ground on quality in this area it will compromise the viability of Network Server and client. Lorax says "Unless...". Kathey
