Return-Path: X-Original-To: apmail-lucene-pylucene-dev-archive@minotaur.apache.org Delivered-To: apmail-lucene-pylucene-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 13A0361A2 for ; Sat, 2 Jul 2011 14:38:45 +0000 (UTC) Received: (qmail 62286 invoked by uid 500); 2 Jul 2011 14:38:44 -0000 Delivered-To: apmail-lucene-pylucene-dev-archive@lucene.apache.org Received: (qmail 62262 invoked by uid 500); 2 Jul 2011 14:38:44 -0000 Mailing-List: contact pylucene-dev-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: pylucene-dev@lucene.apache.org Delivered-To: mailing list pylucene-dev@lucene.apache.org Received: (qmail 62254 invoked by uid 99); 2 Jul 2011 14:38:43 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 02 Jul 2011 14:38:43 +0000 X-ASF-Spam-Status: No, hits=0.7 required=5.0 tests=MIME_QP_LONG_LINE,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [173.228.80.32] (HELO ovaltofu.org) (173.228.80.32) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 02 Jul 2011 14:38:37 +0000 Received: from [192.168.1.10] (AOrleans-552-1-1-152.w90-63.abo.wanadoo.fr [90.63.48.152]) (authenticated bits=0) by ovaltofu.org (8.14.4/8.14.4) with ESMTP id p62EcB1K019216 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for ; Sat, 2 Jul 2011 07:38:13 -0700 (PDT) Subject: Re: [VOTE] Release PyLucene 3.3.0 References: <4E0F07F9.7040901@cheimes.de> <4E0F1B31.7000307@ontrenet.com> From: Andi Vajda Content-Type: text/plain; charset=us-ascii X-Mailer: iPhone Mail (8J2) In-Reply-To: <4E0F1B31.7000307@ontrenet.com> Message-Id: Date: Sat, 2 Jul 2011 16:37:22 +0200 To: "pylucene-dev@lucene.apache.org" Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (iPhone Mail 8J2) X-Virus-Checked: Checked by ClamAV on apache.org On Jul 2, 2011, at 15:20, Darren Govoni wrote: > Without the third 0, how will you version critical patch releases should t= hey be necessary? If the patch comes from Lucene, then I'd use their new version number, as us= ual. If it's a PyLucene fix, its version would go from 3.3-1 to 3.3-2. Andi.. >=20 > On 07/02/2011 09:13 AM, Andi Vajda wrote: >> On Jul 2, 2011, at 13:58, Christian Heimes wrote: >>=20 >>> Am 01.07.2011 14:24, schrieb Andi Vajda: >>>> The PyLucene 3.3.0-1 release closely tracking the recent release of Luc= ene >>>> Java 3.3 is ready. >>>>=20 >>>> A release candidate is available from: >>>> http://people.apache.org/~vajda/staging_area/ >>>>=20 >>>> A list of changes in this release can be seen at: >>>> http://svn.apache.org/repos/asf/lucene/pylucene/branches/pylucene_3_3/C= HANGES >>>>=20 >>>> PyLucene 3.3.0 is built with JCC 2.9 included in these release artifact= s. >>>>=20 >>>> A list of Lucene Java changes can be seen at: >>>> http://svn.apache.org/repos/asf/lucene/dev/tags/lucene_solr_3_3/lucene/= CHANGES.txt >>>>=20 >>>> Please vote to release these artifacts as PyLucene 3.3.0-1. >>> I've tested PyLucene 3.3 with your application, everything still works. >>> I can't comment on new features, though. >>>=20 >>> +1 from me >>>=20 >>> By the way could you please keep a consistent version schema? You are >>> slowly dropping the zero at the end. ;) >>>=20 >>> pylucene-3.1.0-1-src.tar.gz LUCENE_VER=3D3.1.0 >>> pylucene-3.2.0-1-src.tar.gz LUCENE_VER=3D3.2 >>> pylucene-3.3-1-src.tar.gz LUCENE_VER=3D3.3 >> :-) >> I resisted the Lucene Java 0 droppage but it got the best of me. >>=20 >> Andi.. >>=20 >>> Christian