Laura Stewart wrote: > On 9/12/06, Daniel John Debrunner <[EMAIL PROTECTED]> wrote: > >> In both cases the current state of the 10.2 branch is left unchanged wrt >> JDBC 4.0, ie. no removal of JDBC 4.0 from code or documentation. > > If either of these approaches are used, the doc issue needs to be > handled carefully. The JDBC 4.0 information will be in the > documentation. Even if a statement is put into the Release Notes > about this, it is very likely that a user (or 2) will miss the > statement about JDBC 4.0 in the Release Notes and run into some > problems.
So let's nail down the doc problem. I think https://issues.apache.org/jira/browse/DERBY-1271 summarizes the changes. Scroll down past the description to the comments section. You should see a tab marked "Subversion Commits". Click on that and you'll see all the files that were changed for JDBC 4. It looks like 6 files were added to the Reference Guide specifically for the new JDBC 4.0 features: rrefjdbc4_0connection.dita rrefjdbc4_0sqlexception.dita rrefjdbc4_0databaseMetaData.dita rrefjdbc4_0statement.dita rrefjdbc4_0dataSource.dita rrefjdbc4_0summary.dita What if we were to add a short notice to each file along the lines of (the specific wording would need to get nailed down): "This is new jdbc 4 functionality that is only available to developers who build Derby with jdk16". Are there any other key files that would also need a notice? --I'm willing to help put these notices in (and pull them back out when they are no longer needed). > Something should also be posted on the Web Pages for Derby as well. > > I am not entirely comfortable with leaving a feature in the > documentation that is not being delivered. But the source will be there, so the documentation would be useful for anyone who wants to build Derby with jdk16. > If the docs are left as is, then I would prefer a feature release 10.3 > when we formally support JDBC 4.0. I disagree because developers will already have that functionality if they choose to build Derby themselves. The 10.2 maintenance release would just need to be recompiled with jdk16 to enable that jdbc 4 functionality for users. I do agree that we need to do what we can to avoid confusion. -jean
