Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 50075 invoked from network); 3 Mar 2011 21:34:57 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 3 Mar 2011 21:34:57 -0000 Received: (qmail 75488 invoked by uid 500); 3 Mar 2011 21:34:57 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 75422 invoked by uid 500); 3 Mar 2011 21:34:57 -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 75415 invoked by uid 99); 3 Mar 2011 21:34:57 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 03 Mar 2011 21:34:57 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=5.0 tests=ALL_TRUSTED,T_RP_MATCHES_RCVD X-Spam-Check-By: apache.org Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 03 Mar 2011 21:34:56 +0000 Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116]) by hel.zones.apache.org (Postfix) with ESMTP id DE43F4E0D1 for ; Thu, 3 Mar 2011 21:34:36 +0000 (UTC) Date: Thu, 3 Mar 2011 21:34:36 +0000 (UTC) From: "Tiago R. Espinha (JIRA)" To: derby-dev@db.apache.org Message-ID: <163005251.12072.1299188076907.JavaMail.tomcat@hel.zones.apache.org> Subject: [jira] Created: (DERBY-5091) Derby Test and Fix 2011 GSoC Project MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Derby Test and Fix 2011 GSoC Project ------------------------------------ Key: DERBY-5091 URL: https://issues.apache.org/jira/browse/DERBY-5091 Project: Derby Issue Type: Task Reporter: Tiago R. Espinha Assignee: Tiago R. Espinha Priority: Minor This is the JIRA issue where I will be aggregating issues that might be interesting for a student to address in a "test-and-fix project" under my mentoring during a Google Summer of Code project, for this year's edition. Ideally, I would like to have a closed set of issues that are to be addressed by a single student during the whole program before the program itself starts. If you have comments or suggestions, please feel free to comment on this issue. Obviously, in open-source we cannot stop people from working on whichever issues they feel like. I would actually be quite happy if there were students starting work on some of these issues even before the program starts. That will certainly weigh in when the time to make a decision comes. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira