Return-Path: Delivered-To: apmail-jackrabbit-dev-archive@www.apache.org Received: (qmail 13589 invoked from network); 22 Jul 2008 12:32:21 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 22 Jul 2008 12:32:21 -0000 Received: (qmail 24478 invoked by uid 500); 22 Jul 2008 12:32:19 -0000 Delivered-To: apmail-jackrabbit-dev-archive@jackrabbit.apache.org Received: (qmail 24444 invoked by uid 500); 22 Jul 2008 12:32:19 -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 24433 invoked by uid 99); 22 Jul 2008 12:32:19 -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 05:32:19 -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 aklimets@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 12:31:25 +0000 Received: by goobak01.day.com (Postfix, from userid 1212) id 03D9A50838; Tue, 22 Jul 2008 14:30:02 +0200 (CEST) Received: from yw-out-2324.google.com (yw-out-2324.google.com [74.125.46.28]) by goobak01.day.com (Postfix) with ESMTP id 938875081D for ; Tue, 22 Jul 2008 14:30:02 +0200 (CEST) Received: by yw-out-2324.google.com with SMTP id 3so813956ywj.31 for ; Tue, 22 Jul 2008 05:30:47 -0700 (PDT) Received: by 10.143.7.5 with SMTP id k5mr1813586wfi.327.1216729846846; Tue, 22 Jul 2008 05:30:46 -0700 (PDT) Received: by 10.142.188.14 with HTTP; Tue, 22 Jul 2008 05:30:46 -0700 (PDT) Message-ID: Date: Tue, 22 Jul 2008 14:30:46 +0200 From: "Alexander Klimetschek" To: dev@jackrabbit.apache.org Subject: Re: Component releases, proposed solution In-Reply-To: <510143ac0807220351m2a5fcf9bj76aafd128e5317c9@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> X-Virus-Checked: Checked by ClamAV on apache.org On Tue, Jul 22, 2008 at 12:51 PM, Jukka Zitting wrote: > Applied to the Jackrabbit 1.4.x release cycle, this would have given > us the following releases: > > * Jackrabbit 1.4.1, including core 1.4.1 > * Jackrabbit 1.4.2, including core 1.4.2 > * Jackrabbit 1.4.3, including jcr-commons 1.4.1 and jcr-rmi 1.4.1 > * Jackrabbit 1.4.4, including core 1.4.3 > * Jackrabbit 1.4.5, including core 1.4.4 > * Jackrabbit 1.4.6, including core 1.4.5 Generally I agree, but I know that something like jackrabbit 1.4.6 containing a 1.4.5 core jar would be very confusing when users report a problem. Couldn't we make an exception that the most important component jackrabbit-core always gets the same version number as the overall release - which would imply that sometimes core gets a version number increase without an actual code change. Regards, Alex -- Alexander Klimetschek alexander.klimetschek@day.com