Differences between revisions 53 and 54
Revision 53 as of 2006-10-07 23:15:08
Size: 12730
Comment:
Revision 54 as of 2009-09-20 22:12:17
Size: 12775
Editor: localhost
Comment: converted to 1.6 markup
Deletions are marked like this. Additions are marked like this.
Line 2: Line 2:
[[TableOfContents(3)]] <<TableOfContents(3)>>
Line 29: Line 29:
||[http://db.apache.org/derby/derby_downloads.html] || The 10.2 release is available from the Derby download page. Please try it ||
||[http://wiki.apache.org/db-derby/TenTwoSnapshot Snapshot wiki] || Beta description.||
||[[http://db.apache.org/derby/derby_downloads.html]] || The 10.2 release is available from the Derby download page. Please try it ||
||[[http://wiki.apache.org/db-derby/TenTwoSnapshot|Snapshot wiki]] || Beta description.||
Line 39: Line 39:
||[https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&&pid=10594&resolution=-1&fixfor=11187&assigneeSelect=specificgroup&assignee=derby-developers&customfield_12310050=Normal&sorter/field=issuekey&sorter/order=DESC Open Assigned 10.2 issues]|| 10.2 issues that developers plan to fix for 10.2. Please unassign yourself or change the fix version if these won't make 10.2|| ||[[https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&&pid=10594&resolution=-1&fixfor=11187&assigneeSelect=specificgroup&assignee=derby-developers&customfield_12310050=Normal&sorter/field=issuekey&sorter/order=DESC|Open Assigned 10.2 issues]]|| 10.2 issues that developers plan to fix for 10.2. Please unassign yourself or change the fix version if these won't make 10.2||
Line 43: Line 43:
Reviewers and committers: please take a look at the list of [https://issues.apache.org/jira/secure/IssueNavigator.jspa?mode=hide&requestId=12311191 available 10.2 patches]. Reviewers and committers: please take a look at the list of [[https://issues.apache.org/jira/secure/IssueNavigator.jspa?mode=hide&requestId=12311191|available 10.2 patches]].
Line 52: Line 52:
||[http://issues.apache.org/jira/secure/IssueNavigator.jspa?mode=hide&requestId=12311107 Open Blocker 10.2 Issues] ||[http://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&&pid=10594&resolution=-1&fixfor=11187&assigneeSelect=unassigned&customfield_12310050=Blocker&sorter/field=issuekey&sorter/order=DESC Unnassigned Blockers]|| Blocker urgency, must be fixed for 10.2 ||
||[http://issues.apache.org/jira/secure/IssueNavigator.jspa?mode=hide&requestId=12311108 Open Urgent 10.2 Issues] ||[http://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&&pid=10594&resolution=-1&fixfor=11187&assigneeSelect=unassigned&customfield_12310050=Urgent&sorter/field=issuekey&sorter/order=DESC Unassigned Urgent Issues]|| Urgent urgency, must be fixed for 10.2 ||
||[http://issues.apache.org/jira/secure/IssueNavigator.jspa?mode=hide&requestId=12311109 Open Normal 10.2 Issues]|| [http://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&&pid=10594&resolution=-1&fixfor=11187&assigneeSelect=unassigned&customfield_12310050=Normal&sorter/field=issuekey&sorter/order=DESC Unnassigned Normal issues]|| Normal urgency, stretch goals for 10.2 ||
||[http://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&&pid=10594&resolution=-1&fixfor=11187&assigneeSelect=unassigned&sorter/field=issuekey&sorter/order=DESC   Open Low Urgency 10.2 Issues] || [http://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&&pid=10594&resolution=-1&fixfor=11187&assigneeSelect=unassigned&customfield_12310050=Low&sorter/field=issuekey&sorter/order=DESC Unassigned Low Urgency Issues]|| Issues that have been marked as high value candidates for 10.2 but are not release sensitive||
||[[http://issues.apache.org/jira/secure/IssueNavigator.jspa?mode=hide&requestId=12311107|Open Blocker 10.2 Issues]] ||[[http://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&&pid=10594&resolution=-1&fixfor=11187&assigneeSelect=unassigned&customfield_12310050=Blocker&sorter/field=issuekey&sorter/order=DESC|Unnassigned Blockers]]|| Blocker urgency, must be fixed for 10.2 ||
||[[http://issues.apache.org/jira/secure/IssueNavigator.jspa?mode=hide&requestId=12311108|Open Urgent 10.2 Issues]] ||[[http://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&&pid=10594&resolution=-1&fixfor=11187&assigneeSelect=unassigned&customfield_12310050=Urgent&sorter/field=issuekey&sorter/order=DESC|Unassigned Urgent Issues]]|| Urgent urgency, must be fixed for 10.2 ||
||[[http://issues.apache.org/jira/secure/IssueNavigator.jspa?mode=hide&requestId=12311109|Open Normal 10.2 Issues]]|| [[http://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&&pid=10594&resolution=-1&fixfor=11187&assigneeSelect=unassigned&customfield_12310050=Normal&sorter/field=issuekey&sorter/order=DESC|Unnassigned Normal issues]]|| Normal urgency, stretch goals for 10.2 ||
||[[http://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&&pid=10594&resolution=-1&fixfor=11187&assigneeSelect=unassigned&sorter/field=issuekey&sorter/order=DESC|Open Low Urgency 10.2 Issues]] || [[http://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&&pid=10594&resolution=-1&fixfor=11187&assigneeSelect=unassigned&customfield_12310050=Low&sorter/field=issuekey&sorter/order=DESC|Unassigned Low Urgency Issues]]|| Issues that have been marked as high value candidates for 10.2 but are not release sensitive||
Line 59: Line 59:
||[http://issues.apache.org/jira/secure/IssueNavigator.jspa?mode=hide&requestId=12311067 Open 10.2 Issues]|| Issues marked to be fixed in 10.2, sorted by priority. ||
||[http://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&&pid=10594&priority=1&priority=2&status=1&status=3&status=4&sorter/field=issuekey&sorter/order=ASC&sorter/field=updated&sorter/order=DESC&sorter/field=priority&sorter/order=DESCrg/jira/secure/ConfigureReport.jspa?filterid=12310892 Critical/blocker Issues] || Potential critical/blocker issues||
||[http://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&&type=1&pid=10594&component=11407&component=11409&component=11690&component=11410&component=11709&component=11411&component=11415&component=11408&component=11412&component=11414&status=1&status=3&status=4&sorter/field=issuekey&sorter/order=DESC All Open Code Bugs]|| All open bugs regardless of whether they are marked to be fixed in 10.2. ||
||[http://issues.apache.org/jira/browse/DERBY?report=com.atlassian.jira.plugin.system.project:popularissues-panel Jira Popular Issues] || Look at the Jira Popular issues for bugs users would like to see fixed. Bugs are marked with a red dot||
||[[http://issues.apache.org/jira/secure/IssueNavigator.jspa?mode=hide&requestId=12311067|Open 10.2 Issues]]|| Issues marked to be fixed in 10.2, sorted by priority. ||
||[[http://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&&pid=10594&priority=1&priority=2&status=1&status=3&status=4&sorter/field=issuekey&sorter/order=ASC&sorter/field=updated&sorter/order=DESC&sorter/field=priority&sorter/order=DESCrg/jira/secure/ConfigureReport.jspa?filterid=12310892|Critical/blocker Issues]] || Potential critical/blocker issues||
||[[http://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&&type=1&pid=10594&component=11407&component=11409&component=11690&component=11410&component=11709&component=11411&component=11415&component=11408&component=11412&component=11414&status=1&status=3&status=4&sorter/field=issuekey&sorter/order=DESC|All Open Code Bugs]]|| All open bugs regardless of whether they are marked to be fixed in 10.2. ||
||[[http://issues.apache.org/jira/browse/DERBY?report=com.atlassian.jira.plugin.system.project:popularissues-panel|Jira Popular Issues]] || Look at the Jira Popular issues for bugs users would like to see fixed. Bugs are marked with a red dot||
Line 66: Line 66:
[http://issues.apache.org/jira/browse/DERBY-1377 DERBY-1377] is tracking the task to fix the Apache license headers in '''all''' our source files. This is required by Apache for the 10.2 release. This is no small task. If you want to help with this task, see FixingLicenseHeader [[http://issues.apache.org/jira/browse/DERBY-1377|DERBY-1377]] is tracking the task to fix the Apache license headers in '''all''' our source files. This is required by Apache for the 10.2 release. This is no small task. If you want to help with this task, see FixingLicenseHeader
Line 79: Line 79:
||[https://issues.apache.org/jira/secure/IssueNavigator.jspa?mode=hide&requestId=12311088 10.2 Open Documentation Issues]|| 10.2 documentation issues needing attention||
||[https://issues.apache.org/jira/secure/IssueNavigator.jspa?mode=hide&requestId=12311087 All Open Documentation Issues]|| All documentation issues needing attention ||
||[http://wiki.apache.org/db-derby/TenTwoDocReview Documentation Review] || Where to add review comments on the 10.2 documentation ||
||[[https://issues.apache.org/jira/secure/IssueNavigator.jspa?mode=hide&requestId=12311088|10.2 Open Documentation Issues]]|| 10.2 documentation issues needing attention||
||[[https://issues.apache.org/jira/secure/IssueNavigator.jspa?mode=hide&requestId=12311087|All Open Documentation Issues]]|| All documentation issues needing attention ||
||[[http://wiki.apache.org/db-derby/TenTwoDocReview|Documentation Review]] || Where to add review comments on the 10.2 documentation ||
Line 91: Line 91:
 * Vote for issues you want fixed in [http://issues.apache.org/jira/browse/DERBY Jira] to let developers know what you want fixed.
 * Provide test cases that can be incorporated into the [:DerbyTesting:functional tests] once fixed.
 * Vote for issues you want fixed in [[http://issues.apache.org/jira/browse/DERBY|Jira]] to let developers know what you want fixed.
 * Provide test cases that can be incorporated into the [[DerbyTesting|functional tests]] once fixed.
Line 101: Line 101:
 * See [http://db.apache.org/derby/derby_downloads.html Derby Downloads] for instructions on downloading and building Derby
 * See [http://issues.apache.org/jira/browse/DERBY-518#action_12329500 DERBY-518] for svn merge example and request to port to 10.1 branch.
 * See [[http://db.apache.org/derby/derby_downloads.html|Derby Downloads]] for instructions on downloading and building Derby
 * See [[http://issues.apache.org/jira/browse/DERBY-518#action_12329500|DERBY-518]] for svn merge example and request to port to 10.1 branch.

Table of Contents

10.2 Release Summary

Derby 10.2 is a feature release providing many bug fixes plus the following big features:

  • Scrollable Updatable Result Sets
  • JDBC4
  • Grant/Revoke
  • Online Backup
  • Stronger Network Authentication

Release Manager

Rick Hillegas

Last day to commit changes

August 10

Testing and voting

August 14 - October 6

Target release date

October 11

Please download the 10.2 release and test it out. Note that there are four different distributions:

  • bin distribution - contains the documentation, javadoc, and jar files for Derby.
  • lib distribution - contains only the jar files for Derby.
  • lib-debug distribution - contains jar files for Derby with source line numbers.
  • src distribution - contains the Derby source tree at the point which the binaries were built.

http://db.apache.org/derby/derby_downloads.html

The 10.2 release is available from the Derby download page. Please try it

Snapshot wiki

Beta description.

10.2 Bug Fixing and Features

Content for the release

The state of the 10.2 branch is described at the end of this wiki page in the section titled "Patches to Exclude".

10.2 Fixed issues

Issues fixed in 10.2 that are not in the 10.1.3.1 release. RESOLVE: It is not currently possible to generate standard reports or release notes from Jira with just the 10.2 fixes. This is related to the practice of marking Fix Version of 10.2 for issues fixed in earlier releases.

Open Assigned 10.2 issues

10.2 issues that developers plan to fix for 10.2. Please unassign yourself or change the fix version if these won't make 10.2

Bug Fix Candidates

Reviewers and committers: please take a look at the list of available 10.2 patches.

Currently, 10.2 bug fixes go into the mainline. On August 10 we plan to cut a branch. From that time onward, we will need to port fixes from the mainline into the 10.2 branch.

It would be great if we could march through the Open 10.2 issues in urgency order: If you see any issues that look like they cannot be reasonably be fixed for 10.2, change the Fix Version. If you see unassigned issues that are good candidates for 10.2, change the Fix Version to 10.2.

Open Blocker 10.2 Issues

Unnassigned Blockers

Blocker urgency, must be fixed for 10.2

Open Urgent 10.2 Issues

Unassigned Urgent Issues

Urgent urgency, must be fixed for 10.2

Open Normal 10.2 Issues

Unnassigned Normal issues

Normal urgency, stretch goals for 10.2

Open Low Urgency 10.2 Issues

Unassigned Low Urgency Issues

Issues that have been marked as high value candidates for 10.2 but are not release sensitive

Here are views of the issues based on severity:

Open 10.2 Issues

Issues marked to be fixed in 10.2, sorted by priority.

Critical/blocker Issues

Potential critical/blocker issues

All Open Code Bugs

All open bugs regardless of whether they are marked to be fixed in 10.2.

Jira Popular Issues

Look at the Jira Popular issues for bugs users would like to see fixed. Bugs are marked with a red dot

Fixing The Apache License Header

DERBY-1377 is tracking the task to fix the Apache license headers in all our source files. This is required by Apache for the 10.2 release. This is no small task. If you want to help with this task, see FixingLicenseHeader

How To Fix a Bug for the 10.2 Release

The following work flow can help ensure fixes get committed efficiently.

  1. Pick a bug you want to fix and fix it in the trunk.
  2. Submit your patch for the trunk.
  3. Mark the issue resolved only after the fix is in the trunk, and has been merged into the 10.2 branch. The fixin fields should be marked as 10.3 and 10.2.1.

10.2 Documentation Issues and Reviews

Please contribute documentation, also:

10.2 Open Documentation Issues

10.2 documentation issues needing attention

All Open Documentation Issues

All documentation issues needing attention

Documentation Review

Where to add review comments on the 10.2 documentation

10.2 Testing

Other Ways To Help

Besides making code changes in Derby, there are lots of other ways to help.

  • Vote for issues you want fixed in Jira to let developers know what you want fixed.

  • Provide test cases that can be incorporated into the functional tests once fixed.

  • Review and test patches that are submitted to the derby-dev list or Jira.
  • Test the TenTwoSnapshot. Record your results on TenTwoApplicationTesting. Try new features. Flush out all the issues before release.

  • Participate in the Derby RegressionSearchAndDestroy contest

Tips

  • See Derby Downloads for instructions on downloading and building Derby

  • See DERBY-518 for svn merge example and request to port to 10.1 branch.

  • Send any questions about release status or fixing bugs to derby-dev

Thank You 10.2 Volunteers

51 so far representing at least 4 continents.

Developers who have contributed 10.2 fixes

A B , Anders Morken , Andreas Korneliussen , Andrew McIntyre , Anurag Shekhar , Bernt M. Johnsen , Bryan Pendleton , Dag H. Wanvik , Daniel John Debrunner , David Van Couvering , Deepa Remesh , Dyre Tjeldvoll , Eric Radzinski , Fernanda Pizzorno , Francois Orsini , Halley Pacheco de Oliveira , Håvard Mork , Jack Klebanoff , Jean T. Anderson , Jeff Levitt , John H. Embretsen , Kathey Marsden , Kim Haase, Knut Anders Hatlen , Kristian Waagan , Lance Andersen , Laura Stewart , Mamta A. Satoor , Manish Khettry , Manjula Kutty , Mathias Herberts , Mayuresh Nirhali , Michelle Caisse , Mike Matrigali , Myrna van Lunteren , Olav Sandstaa , Ole Solberg , Oyvind Bakksjo , Philip Wilder , Rajesh Kartha , Ramandeep Kaur , Rick Hillegas , Satheesh Bandaram , Sunitha Kambhampati , Suresh Thalamati , Susan Cline , Tomohito Nakayama , Unassigned , V.Narayanan , Vemund Østgaard , Yip Ng , Øystein Grøvlen

Additional Contributors

Many Contributions like testing or committing patches don't show up on a JIRA query and need to be added manually. Please add those missed by the fix query.

Henri van de Scheur, Michael Bouschen

Patches to Exclude

Now that we have moved from beta to release candidates, the 10.2 branch control policy has changed. At this time, we want to be cautious about what goes into the branch. No more bulk merges will be done. Instead, we will only hand-port the changes that are absolutely necessary to stabilize the release candidates.

During the beta period, we tried to strike the right balance between rapid bug fixing and branch control. During the the beta period, patches accumulated in the trunk without being ported to the 10.2 branch immediately. On a weekly basis, we bulk merged these patches to the 10.2 branch. However, we had to keep track of the patches which weren't ported. Here are the unported patches:

Subversion Revision

Description

430857

Bump trunk's version number to 10.3

430946

Patch up canons to agree with version bump

431744

Remove upgrade test for 10.1 to 10.2 path

439137

DERBY-1566 Update "SQL error messages and exceptions" section of the Reference Guide with sqlstates and messages in the trunk.

447815

DERBY-801 Allow parallel access to data files.

447856

DERBY-801 Backed out changes for DERBY-733.

448465

Javadoc warning in the 801 code.

All changes on the trunk from the time the 10.2 branch was created and ending with subversion revision 448950 for code and 448988 for documentation (excluding the above) were merged into the 10.2 branch. Bulk merges occurred on August 18, August 25, September 1, September 8, September 15, and September 22, 2006.

Building the Optional JDBC4 Support

Due to licensing restrictions, the 10.2 release does not contain compiled support for JDBC4. Instead, when you run Derby 10.2 on JDK 1.6, you will see Derby's JDBC3 drivers. If you would like to test-drive the JDBC4 drivers, you may build the optional JDBC4 support yourself. Please do the following:

  • Download the -bin and -src distributions of Derby 10.2.1and unzip them.
  • Set the environment variable DERBY_HOME in your shell environment to the location where you have unzipped the -bin distribution.
  • Set the environment variable JAVA_HOME in your shell environment to the location of a JDK 1.6 JVM. Make sure that this is the version of JDK 1.6 mentioned in the "JDBC 4.0 Support" section of the Release Notes. Derby 10.2.1 may not compile or run correctly if you use a different version of the JDK.
  • In your shell, change directory into the tools/jdbc4 directory where you unzipped the -src distribution.
  • Run the update-with-jdbc4 script (or batch file on Windows), and the jars in $DERBY_HOME/lib will be updated with the necessary JDBC 4 support classes.

You must use build 99 of the 1.6 JDK in order to build and exercise the JDBC4 drivers in the 10.2.1.6 release.

After the 10.2.1.6 release was generated, the Ease of Development feature was removed from the JDBC4 spec. The Derby trunk and 10.2 branch were updated accordingly. If you obtain the source code from the 10.2 branch at or after subversion revision 453926, the JDBC4 support will compile and run against build 101 or later of the 1.6 VM. That subversion stamp corresponds to the 10.2.1.7 snapshot. To build this state of the 10.2 branch with JDBC4 support, please see the instructions in BUILDING.txt.

TenTwoRelease (last edited 2009-09-20 22:12:17 by localhost)