Return-Path: Delivered-To: apmail-db-derby-commits-archive@www.apache.org Received: (qmail 38817 invoked from network); 4 Mar 2006 00:32:36 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 4 Mar 2006 00:32:36 -0000 Received: (qmail 82785 invoked by uid 500); 4 Mar 2006 00:33:21 -0000 Delivered-To: apmail-db-derby-commits-archive@db.apache.org Received: (qmail 82585 invoked by uid 500); 4 Mar 2006 00:33:20 -0000 Mailing-List: contact derby-commits-help@db.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: "Derby Development" List-Id: Delivered-To: mailing list derby-commits@db.apache.org Received: (qmail 82566 invoked by uid 99); 4 Mar 2006 00:33:20 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [192.87.106.226] (HELO ajax.apache.org) (192.87.106.226) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 03 Mar 2006 16:33:20 -0800 Received: from ajax.apache.org (ajax.apache.org [127.0.0.1]) by ajax.apache.org (Postfix) with ESMTP id 3630DDF for ; Sat, 4 Mar 2006 01:32:59 +0100 (CET) Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: Apache Wiki To: derby-commits@db.apache.org Date: Sat, 04 Mar 2006 00:32:59 -0000 Message-ID: <20060304003259.32619.91234@ajax.apache.org> Subject: [Db-derby Wiki] Update of "DerbyCommitHowTo" by BryanPendleton X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N 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 BryanPendleton: http://wiki.apache.org/db-derby/DerbyCommitHowTo ------------------------------------------------------------------------------ = Committing patches to the Derby Subversion Repository = - Oyvind Bakksjo compiled this set of notes to guide Derby committers through the low-level mechanics of committing a change to Derby. These notes are best read within the larger context of the DerbyCommitProcess. + Based on a previous document by Oyvind Bakksjo, here are a set of notes to guide Derby committers through the low-level mechanics of committing a change to Derby. These notes are best read within the larger context of the DerbyCommitProcess. Committing contributions from others is not as straightforward as one might think. This mainly stems from the fact that there is an {{{svn diff}}} command, but there is no {{{svn patch}}} command. There are a number of things to remember; if not done carefully, you might end up doing partial commits that may break the build. This page attempts to give a recipe for safely committing code contributions. @@ -31, +31 @@ * possibly running some or all of the [http://svn.apache.org/repos/asf/db/derby/code/trunk/java/testing/README.htm regression test suites], as the committer deems relevant. Check that tests pass. If they do not: * Check the nightly/tinderbox for the same failure. * Verify that the failure is not caused by the patch. - * Commit the patch with {{{svn commit}}}. Use either {{{--message}}}, {{{--file}}} or {{{--editor-cmd}}}. Include the following in the commit message: + * Commit the patch with {{{svn commit}}}. Use either {{{--message}}}, {{{--file}}} or {{{--editor-cmd}}}. Include the following in the commit log message: * The ID of the JIRA issue. Make sure you use the format DERBY-NNN so that JIRA picks it up. * Some text explaining what the patch does (typically snipped from the JIRA issue). * The contributor's name/email. - * Send out an email to let people know you have committed the patch. This is done automatically if you post the information as a comment to the JIRA issue. + * Notify the contributor and the community that the patch has been committed, according to the DerbyCommitProcess.