Re: [Db-derby Wiki] Update of "DerbyDevActivities" by SatheeshBandaram

[Satheesh Bandaram]

Daniel John Debrunner wrote: I'm curious how do you think it would be useful? For status updates... If I look at the list after long time, I know which items I need to update more easily. Guess feature name might be enough to remind me. :-) I have changed the page to have three tables now. (http://wiki.apache.org/db-derby/DerbyDevActivities) One for new features, second for internal improvements and last one for bugs or other items that may need release notes mention. I wasn't sure where to put information that should go into release notes until very close to release date. I do like your other idea about breaking the table into two... I did see several improvements that don't require functionality changes was thinking where to put them. About JDBC 4.0, isn't that some kind of functionality change, since Derby can now be used on 1.6 platforms? (pre-release) Derby should be able to run on 1.6 without any JDBC 4.0 support, the JDBC 3.0 driver would still work. I sew it as not a feature because it doesn't provide any useful features, since I believe the JDBC 4.0 driver is currently only stubs. I can move it to Improvements table.... I thought without the patch, Derby may not run on JDK 1.6 because of changes in the interfaces and the use of generics? Satheesh