Return-Path: Delivered-To: apmail-lucene-java-dev-archive@www.apache.org Received: (qmail 13290 invoked from network); 13 Apr 2010 20:01:38 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 13 Apr 2010 20:01:38 -0000 Received: (qmail 6697 invoked by uid 500); 13 Apr 2010 20:01:37 -0000 Delivered-To: apmail-lucene-java-dev-archive@lucene.apache.org Received: (qmail 6656 invoked by uid 500); 13 Apr 2010 20:01:37 -0000 Mailing-List: contact java-dev-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: java-dev@lucene.apache.org Delivered-To: mailing list java-dev@lucene.apache.org Received: (qmail 6649 invoked by uid 99); 13 Apr 2010 20:01:37 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 13 Apr 2010 20:01:37 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of gsiasf@gmail.com designates 209.85.221.197 as permitted sender) Received: from [209.85.221.197] (HELO mail-qy0-f197.google.com) (209.85.221.197) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 13 Apr 2010 20:01:28 +0000 Received: by qyk35 with SMTP id 35so7002275qyk.11 for ; Tue, 13 Apr 2010 13:01:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:from:mime-version :content-type:subject:date:in-reply-to:to:references:message-id :x-mailer; bh=sSRVBw5dJ8PFv7aXnKNu4EY+FccoLzfoY64h2I/lUoA=; b=nvuvCWfJXh5ScODV5VOul9p7QT7jwJRYTUUnb3Hq1wvnhF7JvK2DaYZUzwIEU4rDwX OrJRz8Sfi79W/sToq4ECGwOkeD1zl/kfGcRCGv42Buk5NQH26HAp/MztUAicBHVFN3Sl r2E8ATnFoJ+vBr58peYLr+mkMuj2b24M8K2cc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:from:mime-version:content-type:subject:date:in-reply-to:to :references:message-id:x-mailer; b=EoTLyG/u+E247GqTiFixqaUlRcikSEvtG0zLXFVfBClP9qpgZf+M4TiYHXSAJwvDxf uWsJPfml5NTUwIGMSMHs7kVTj1RQrR4YU/grYGiGSgtraYI5mFtMbSDTpgrwb5lXM7kp 9a7FJtI5JRzwCwdRIYQXSgGQqwkScJhgy0Gn0= Received: by 10.229.88.72 with SMTP id z8mr292857qcl.3.1271188867304; Tue, 13 Apr 2010 13:01:07 -0700 (PDT) Received: from [10.0.0.77] (adsl-065-013-152-164.sip.rdu.bellsouth.net [65.13.152.164]) by mx.google.com with ESMTPS id y41sm7937137qce.5.2010.04.13.13.01.05 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 13 Apr 2010 13:01:06 -0700 (PDT) Sender: Grant Ingersoll From: Grant Ingersoll Mime-Version: 1.0 (Apple Message framework v1078) Content-Type: multipart/alternative; boundary=Apple-Mail-1485-823888616 Subject: Re: Proposal about Version API "relaxation" Date: Tue, 13 Apr 2010 16:01:04 -0400 In-Reply-To: To: java-dev@lucene.apache.org References: <016001cadb28$3c70ca40$b5525ec0$@de> Message-Id: X-Mailer: Apple Mail (2.1078) X-Virus-Checked: Checked by ClamAV on apache.org --Apple-Mail-1485-823888616 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On Apr 13, 2010, at 2:09 PM, Shai Erera wrote: >=20 > And I guess that what bothers me the most is that it feels to me like = we're trying to protect people from stuff we haven't yet received = complaints on (at least none that I'm aware of), I think we have, they just aren't explicitly stated b/c most users don't = necessarily grasp the subtleties of tokens at this level. We have long = talked and had questions about how to handle bug fixes in Analyzers. > while we're hurting the programming experience of others ... almost = recklessly. Wearing my trainer hat as someone who has to explain this stuff to = newbies on a regular basis, I agree, I think VERSION does hurt the = programming experience (although, I don't agree it is even close to = reckless) at least initially and the issue was more easily dealt with = through CHANGES.txt and letting people know there is a bug fix that will = require re-indexing. That being said, I'm not sure I like the static = proposal. Separating out the analyzers more seems good on paper and = versioning individual ones somehow. -Grant= --Apple-Mail-1485-823888616 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii

And I guess that what bothers me the most is = that it feels to me like we're trying to protect people from stuff we = haven't yet received complaints on (at least none that I'm aware = of),

I think we have, they = just aren't explicitly stated b/c most users don't necessarily grasp the = subtleties of tokens at this level.  We have long talked and had = questions about how to handle bug fixes in = Analyzers.

= while we're hurting the programming experience of others ... almost = recklessly.

Wearing my = trainer hat as someone who has to explain this stuff to newbies on a = regular basis, I agree, I think VERSION does hurt the programming = experience (although, I don't agree it is even close to reckless) at = least initially and the issue was more easily dealt with through = CHANGES.txt and letting people know there is a bug fix that will require = re-indexing.  That being said, I'm not sure I like the static = proposal.   Separating out the analyzers more seems good on paper = and versioning individual ones = somehow.

-Grant
= --Apple-Mail-1485-823888616--