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 "TenTwoRelease" by KatheyMarsden
Date Sun, 30 Jul 2006 16:10:05 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:
http://wiki.apache.org/db-derby/TenTwoRelease

------------------------------------------------------------------------------
  === Content for the release ===
  
  || 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.||
+ ||[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||
  
  === Bug Fix Candidates ===
  Currently, 10.2 bug fixes go into the mainline. On August 10 we plan
@@ -40, +41 @@

  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.
  
- ||[http://issues.apache.org/jira/secure/IssueNavigator.jspa?mode=hide&requestId=12311107
Open Blocker 10.2 Issues]|| 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]|| 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]|| Normal urgency, stretch goals for 10.2 ||
- 
+ ||[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||
  
  Here are views of the issues based on severity:
  
@@ -55, +56 @@

  
  === How To Fix a Bug for the 10.2 Release ===
  
- The following work flow can help ensure fixes get committed efficiently. 
+ 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.
   1. Mark the issue resolved only after the fix is in the trunk. The fixin fields should
be marked as 10.2.1.0.
@@ -84, +85 @@

   * Send any questions about release status or fixing bugs to derby-dev
  
  == Thank You 10.2 Volunteers ==
- 42 so far representing at least 4 continents.  
+ 42 so far representing at least 4 continents.
  
  === Developers who have contributed 10.2 fixes ===
  A B ,

Mime
View raw message