db-derby-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Db-derby Wiki] Update of "TenOneThreeRelease" by KatheyMarsden
Date Tue, 25 Apr 2006 23:51:03 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Db-derby Wiki" for change notification.

The following page has been changed by KatheyMarsden:

New page:
'''Table of Contents'''

== 10.1.3 Release  Summary ==

The Derby 10.1.3 release is a maintenance release and will provide users with lots of bug
fixes and other quality and performance improvements. 

||Release Manager   	    || Andrew McIntyre||
||Last day to commit changes||  June 8 ||
||Testing and voting begins ||  June 9 ||
||Target release date       ||  June 28||
Tenative Release Notes]  ||  All fixes already in 10.1.3 and marked fixin 10.1.3||

== 10.1.3 Bug Fixing ==

===  Planned Content for the Release  ===
10.1.3 Fixed Issues]  || Any issue fixed on the 10.1 branch since release.||
10.1.3 Open Issues ]      || Issues developers have marked fix in 10.1.3 and plan to fix for
the release. ||

=== Bug Fix Candidates ===

Select a bug you want to from one of the following lists.  Fixes in the 10.1 maintenance branch
should be ones that you feel confident are very stable and pose low risk of regression. Not
all of the bugs on these lists qualify and need dto be evaluated on an individual basis:

10.1 Open Code Bugs]|| Code bugs that affect 10.1 ||
|| Fixed bugs in 10.2||Many bugs fixed in 10.2 can easily be ported to 10.1 /!\ Sorry no list
yet. Coming soon. ||
Jira Popular Issues] || Look at the Jira Popular issues for bugs users would like to see fixed.
 Bugs are marked with a red dot||

=== How to fix a bug for the 10.1.3 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.
 1. Submit your patch for the trunk. Mark the fix version as 10.1.3 if you would like it to
go to the 10.1 branch.
 1. Merge the change to 10.1.
    After your patch has been committed, test your change on the 10.1 branch, submit your
10.1 testing results along with either
   1. The svn command(s) to merge your trunk change to 10.1. 
      See ["MoveAChangeBetweenBranches"] for details.
   1. A 10.1 patch if the merge was not automatic.
 1. Mark the issue resolved only after the fix is in both the trunk and 10.1 branch. The fixin
fields should be marked as
    * - So that it will be in the bug fix release release notes.
    * 10.1.2.x - As shown by sysinfo on the 10.1 branch
    * 10.2.0.x - As shown by sysinfo on the trunk

== Other Ways To Help ==
If you do not want to make code changes in Derby but still want to help improve the quality
of the release and move it along. There are lots of other ways to help.

 * Vote for issues you want fixed in Jira to let developers know what you want fix.
 * Provide test cases that can be incorporated into the functional tests once fixed.
 * Review and test patches that are submitted to the list
 * Test and vote on the 10.1.3 release candidate when it comes out.
 * Test the  snapshot release 

== 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

View raw message