Return-Path: 
 <derby-dev-return-83847-apmail-db-derby-dev-archive=db.apache.org@db.apache.org>
Delivered-To: apmail-db-derby-dev-archive@www.apache.org
Received: (qmail 95042 invoked from network); 13 Jan 2011 20:40:54 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3)
  by minotaur.apache.org with SMTP; 13 Jan 2011 20:40:54 -0000
Received: (qmail 53094 invoked by uid 500); 13 Jan 2011 20:40:54 -0000
Delivered-To: apmail-db-derby-dev-archive@db.apache.org
Received: (qmail 53068 invoked by uid 500); 13 Jan 2011 20:40:54 -0000
Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:derby-dev-help@db.apache.org>
List-Unsubscribe: <mailto:derby-dev-unsubscribe@db.apache.org>
List-Post: <mailto:derby-dev@db.apache.org>
List-Id: <derby-dev.db.apache.org>
Reply-To: <derby-dev@db.apache.org>
Delivered-To: mailing list derby-dev@db.apache.org
Received: (qmail 53061 invoked by uid 99); 13 Jan 2011 20:40:54 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 13 Jan 2011 20:40:53 +0000
X-ASF-Spam-Status: No, hits=2.9 required=10.0
	tests=HTML_MESSAGE,SPF_NEUTRAL
X-Spam-Check-By: apache.org
Received-SPF: neutral (athena.apache.org: local policy)
Received: from [32.97.110.158] (HELO e37.co.us.ibm.com) (32.97.110.158)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 13 Jan 2011 20:40:45 +0000
Received: from d03relay05.boulder.ibm.com (d03relay05.boulder.ibm.com
 [9.17.195.107])
	by e37.co.us.ibm.com (8.14.4/8.13.1) with ESMTP id p0DKbmXO030533
	for <derby-dev@db.apache.org>; Thu, 13 Jan 2011 13:37:48 -0700
Received: from d03av02.boulder.ibm.com (d03av02.boulder.ibm.com
 [9.17.195.168])
	by d03relay05.boulder.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id
 p0DKeEjV035934
	for <derby-dev@db.apache.org>; Thu, 13 Jan 2011 13:40:14 -0700
Received: from d03av02.boulder.ibm.com (loopback [127.0.0.1])
	by d03av02.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id
 p0DKeEwP017464
	for <derby-dev@db.apache.org>; Thu, 13 Jan 2011 13:40:14 -0700
Received: from [127.0.0.1] (sig-9-48-114-82.mts.ibm.com [9.48.114.82])
	by d03av02.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id
 p0DKeCm1017356
	for <derby-dev@db.apache.org>; Thu, 13 Jan 2011 13:40:13 -0700
Message-ID: <4D2F632F.6040506@sbcglobal.net>
Date: Thu, 13 Jan 2011 12:40:15 -0800
From: Kathey Marsden <kmarsdenderby@sbcglobal.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
 rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: derby-dev@db.apache.org
Subject: Jira cleanup and triage
Content-Type: multipart/alternative;
 boundary="------------070507090900020505090705"

This is a multi-part message in MIME format.
--------------070507090900020505090705
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

I started the process of Jira cleanup and  see that many have been 
working on their own issues by looking at the reports in the Personal 
View column on :
http://wiki.apache.org/db-derby/DerbyJiraReports#Jira_Maintenance_Reports

Thank you and please do this if you have not already.  The command to 
link an svn change to a fix version on trunk is:
svn cat -r <svn version> <path to 
trunk>/tools/ant/properties/release.properties

I apologize for all the related spam.  Unfortunately it has been a long 
time since we have done this so it is generating a lot of mail. In 
continuation of the effort  I plan the following more broad based bulk 
changes tomorrow after folks finish their individual cleanup,  which 
happily can be made without email, but may not be very exact.

1) For fixed issues with no fix versions prior to the 10.5 release date 
I would like to set the fix version based on the resolution date and 
whether it was before the initial release date on the branch. (169 of 211)

2) For resolved issues that are not closed , I would like to close 
anything resolved before Jan 1, 2010.

For triage of  the unresolved issues (there are 1084, 478 bugs), what is 
needed is to review each issue, make sure it is current and relevant and 
all the proper check boxes are set, newcomer, high value fix, repro 
available etc.  Perhaps we can break this up by component if anyone else 
is interested in this exercise.   Please respond to this thread with the 
ones you would like to volunteer look at.  The criteria for high value 
fix is here:
http://wiki.apache.org/db-derby/HighValueFixCandidates

Also be on the lookout and mark  as newcomer  any issues that would be 
good for new developers coming on the project.

Thanks for your patience especially with the mail.  Quote of the day 
comes from Dag on IRC this morning...

"entropy is always lurking if we don't make some periodic cleanups..."

Kathey







--------------070507090900020505090705
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
  </head>
  <body text="#000000" bgcolor="#ffffff">
    I started the process of Jira cleanup and&nbsp; see that many have been
    working on their own issues by looking at the reports in the
    Personal View column on :<br>
<a class="moz-txt-link-freetext" href="http://wiki.apache.org/db-derby/DerbyJiraReports#Jira_Maintenance_Reports">http://wiki.apache.org/db-derby/DerbyJiraReports#Jira_Maintenance_Reports</a><br>
    <br>
    Thank you and please do this if you have not already.&nbsp; The command
    to link an svn change to a fix version on trunk is:<br>
    <span> svn cat -r &lt;svn version&gt; &lt;path to
      trunk&gt;/tools/ant/</span><span>properties/release.<wbr>properties</span><br>
    <br>
    I apologize for all the related spam.&nbsp; Unfortunately it has been a
    long time since we have done this so it is generating a lot of mail.
    In continuation of the effort&nbsp; I plan the following more broad based
    bulk changes tomorrow after folks finish their individual cleanup,&nbsp;
    which happily can be made without email, but may not be very exact.
    <br>
    <br>
    1) For fixed issues with no fix versions prior to the 10.5 release
    date I would like to set the fix version based on the resolution
    date and whether it was before the initial release date on the
    branch. (169 of 211)<br>
    <br>
    2) For resolved issues that are not closed , I would like to close
    anything resolved before Jan 1, 2010.<br>
    <br>
    For triage of&nbsp; the unresolved issues (there are 1084, 478 bugs),
    what is needed is to review each issue, make sure it is current and
    relevant and all the proper check boxes are set, newcomer, high
    value fix, repro available etc.&nbsp; Perhaps we can break this up by
    component if anyone else is interested in this exercise. &nbsp; Please
    respond to this thread with the ones you would like to volunteer
    look at.&nbsp; The criteria for high value fix is here:<br>
    <a class="moz-txt-link-freetext" href="http://wiki.apache.org/db-derby/HighValueFixCandidates">http://wiki.apache.org/db-derby/HighValueFixCandidates</a><br>
    <br>
    Also be on the lookout and mark&nbsp; as newcomer&nbsp; any issues that would
    be good for new developers coming on the project. <br>
    <br>
    Thanks for your patience especially with the mail.&nbsp; Quote of the day
    comes from Dag on IRC this morning...<br>
    <br>
    "<span>entropy is always lurking if we don't make some periodic
      cleanups..."<br>
      <br>
      Kathey<br>
    </span><br>
    <br>
    <br>
    <br>
    <br>
    <br>
  </body>
</html>

--------------070507090900020505090705--