From isis-dev-return-2104-apmail-incubator-isis-dev-archive=incubator.apache.org@incubator.apache.org Sun Jul 17 16:24:12 2011 Return-Path: X-Original-To: apmail-incubator-isis-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-isis-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 94DE26E75 for ; Sun, 17 Jul 2011 16:24:12 +0000 (UTC) Received: (qmail 70726 invoked by uid 500); 17 Jul 2011 16:24:12 -0000 Delivered-To: apmail-incubator-isis-dev-archive@incubator.apache.org Received: (qmail 70696 invoked by uid 500); 17 Jul 2011 16:24:12 -0000 Mailing-List: contact isis-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: isis-dev@incubator.apache.org Delivered-To: mailing list isis-dev@incubator.apache.org Received: (qmail 70688 invoked by uid 99); 17 Jul 2011 16:24:12 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 17 Jul 2011 16:24:12 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of dkhaywood@gmail.com designates 74.125.82.43 as permitted sender) Received: from [74.125.82.43] (HELO mail-ww0-f43.google.com) (74.125.82.43) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 17 Jul 2011 16:24:04 +0000 Received: by wwi18 with SMTP id 18so2310534wwi.0 for ; Sun, 17 Jul 2011 09:23:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:reply-to:organization:user-agent:mime-version :to:subject:content-type; bh=PdTDVj7ibHCbrkzJsnbtOEWJGZDK/MEEAwDaq1FTh2s=; b=R94qqSXB4UoqN/GsGFgjUwM7BlIxBtu79rSmol5rObFBVT3LAA78Z59ckejMH1ZjJV wmHxBL0tMcx+UnPzTh5pWZO3GFowEwd8MIwLy+wgmJUvVbm/dOSMtZeG+PE4z7hZ8IrZ pb6urFKJ9Etni6neWc+7Ylq1DvyaTwiCzPUSI= Received: by 10.227.59.10 with SMTP id j10mr285959wbh.96.1310919823149; Sun, 17 Jul 2011 09:23:43 -0700 (PDT) Received: from [192.168.178.66] (host86-159-29-98.range86-159.btcentralplus.com [86.159.29.98]) by mx.google.com with ESMTPS id fx12sm2733787wbb.8.2011.07.17.09.23.41 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 17 Jul 2011 09:23:42 -0700 (PDT) Message-ID: <4E230C92.7020006@gmail.com> Date: Sun, 17 Jul 2011 17:23:46 +0100 From: Dan Haywood Reply-To: dan@haywood-associates.co.uk Organization: Haywood Associates Ltd. User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-GB; rv:1.9.2.18) Gecko/20110616 Lightning/1.0b2 Thunderbird/3.1.11 MIME-Version: 1.0 To: "isis-dev@incubator.apache.org" Subject: commit messages and JIRA Content-Type: multipart/mixed; boundary="------------090101090205090607060202" --------------090101090205090607060202 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Now that we have a first release out, I'd like to ensure that there's some traceability in changes being made... That way we can be sure that our release notes for subsequent releases will be reasonably comprehensive, as well as meaning that users will gain confidence in us as being a properly-run project. So, what I'd like to propose that any commits that we do to the codebase are cross-referenced to a JIRA ticket. For example, if working on ISIS-105, then the commit message should be something like: "ISIS-105: sorted out formatting". Opinions? Thanks Dan --------------090101090205090607060202--