Return-Path: Delivered-To: apmail-jackrabbit-dev-archive@www.apache.org Received: (qmail 51158 invoked from network); 22 Jul 2008 15:52:32 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 22 Jul 2008 15:52:32 -0000 Received: (qmail 57907 invoked by uid 500); 22 Jul 2008 15:52:30 -0000 Delivered-To: apmail-jackrabbit-dev-archive@jackrabbit.apache.org Received: (qmail 57879 invoked by uid 500); 22 Jul 2008 15:52:30 -0000 Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@jackrabbit.apache.org Delivered-To: mailing list dev@jackrabbit.apache.org Received: (qmail 57868 invoked by uid 99); 22 Jul 2008 15:52:30 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 22 Jul 2008 08:52:30 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of tmueller@day.com designates 62.192.10.254 as permitted sender) Received: from [62.192.10.254] (HELO goobak01.day.com) (62.192.10.254) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 22 Jul 2008 15:51:35 +0000 Received: by goobak01.day.com (Postfix, from userid 1212) id 7E98150831; Tue, 22 Jul 2008 17:51:12 +0200 (CEST) Received: from yx-out-2324.google.com (yx-out-2324.google.com [74.125.44.30]) by goobak01.day.com (Postfix) with ESMTP id 1A4315081D for ; Tue, 22 Jul 2008 17:51:11 +0200 (CEST) Received: by yx-out-2324.google.com with SMTP id 8so372334yxg.31 for ; Tue, 22 Jul 2008 08:51:39 -0700 (PDT) Received: by 10.151.145.17 with SMTP id x17mr5684420ybn.20.1216741899175; Tue, 22 Jul 2008 08:51:39 -0700 (PDT) Received: by 10.151.84.3 with HTTP; Tue, 22 Jul 2008 08:51:39 -0700 (PDT) Message-ID: <91f3b2650807220851i7ee08859laca352a45fd9975c@mail.gmail.com> Date: Tue, 22 Jul 2008 08:51:39 -0700 From: "=?ISO-8859-1?Q?Thomas_M=FCller?=" Sender: tmueller@day.com To: dev@jackrabbit.apache.org Subject: Re: Component releases, proposed solution In-Reply-To: <510143ac0807220803y684a5948ga8c560f0f49b04f7@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <510143ac0807220351m2a5fcf9bj76aafd128e5317c9@mail.gmail.com> <4885F30D.30503@apache.org> <510143ac0807220803y684a5948ga8c560f0f49b04f7@mail.gmail.com> X-Google-Sender-Auth: 3521aa993fd5be27 X-Virus-Checked: Checked by ClamAV on apache.org Hi, > Alternatively, how about if the modified component always got the top > level version number? That way we'd have gaps in the component version > numbers, but it would always be easy to correlate the component > version number with the top-level release that first contained it. +1 for the 'gap version schema'. Regards, Thomas