Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 16323 invoked from network); 7 Jul 2006 21:29:41 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 7 Jul 2006 21:29:41 -0000 Received: (qmail 96290 invoked by uid 500); 7 Jul 2006 21:29:41 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 96255 invoked by uid 500); 7 Jul 2006 21:29:40 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 96245 invoked by uid 99); 7 Jul 2006 21:29:40 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 07 Jul 2006 14:29:40 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: neutral (asf.osuosl.org: local policy) Received: from [204.174.16.201] (HELO mailout1.parasun.com) (204.174.16.201) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 07 Jul 2006 14:29:31 -0700 Received: from cpe-24-143-157-032.cable.alamedanet.net ([24.143.157.32] helo=[127.0.0.1]) by mailout1.parasun.com with esmtp (Exim 4.54) id 1Fyxsj-0003NJ-SP for derby-dev@db.apache.org; Fri, 07 Jul 2006 14:29:02 -0700 Message-ID: <44AED21A.7060703@amberpoint.com> Date: Fri, 07 Jul 2006 14:28:58 -0700 From: Bryan Pendleton User-Agent: Thunderbird 1.5.0.4 (Windows/20060516) MIME-Version: 1.0 To: derby-dev@db.apache.org Subject: DERBY-396: Does it make sense to break this into multiple sub-tasks? Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N I'm thinking that it would make sense to break DERBY-396 down into multiple sub-tasks. I think this would make it easier to track and monitor incremental progress in this area over time. I am thinking that the following list would be a reasonable set of sub-tasks to file. 1) drop column 2) rename column 3) change column from null to not null, or vice versa 4) change column default value 5) change column datatype Does it sound like a good plan to file 5 JIRA sub-tasks per the above? thanks, bryan