Return-Path: Delivered-To: apmail-lucene-solr-dev-archive@minotaur.apache.org Received: (qmail 17745 invoked from network); 18 Mar 2010 17:13:18 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 18 Mar 2010 17:13:18 -0000 Received: (qmail 4576 invoked by uid 500); 18 Mar 2010 17:13:18 -0000 Delivered-To: apmail-lucene-solr-dev-archive@lucene.apache.org Received: (qmail 4437 invoked by uid 500); 18 Mar 2010 17:13:18 -0000 Mailing-List: contact solr-dev-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: solr-dev@lucene.apache.org Delivered-To: mailing list solr-dev@lucene.apache.org Received: (qmail 4429 invoked by uid 99); 18 Mar 2010 17:13:18 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 18 Mar 2010 17:13:18 +0000 X-ASF-Spam-Status: No, hits=0.7 required=10.0 tests=RCVD_IN_DNSWL_NONE,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [74.125.83.48] (HELO mail-gw0-f48.google.com) (74.125.83.48) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 18 Mar 2010 17:13:11 +0000 Received: by gwj17 with SMTP id 17so1143135gwj.35 for ; Thu, 18 Mar 2010 10:12:50 -0700 (PDT) MIME-Version: 1.0 Received: by 10.151.95.13 with SMTP id x13mr4162697ybl.30.1268932370122; Thu, 18 Mar 2010 10:12:50 -0700 (PDT) In-Reply-To: <8f0ad1f31003180926w2b0a80b3i25fdea9a33a68e9c@mail.gmail.com> References: <748361B8-3282-470B-B9F5-561A07D55DEA@apache.org> <05DEB13A-564B-4E61-AB67-17D5749BCDC7@apache.org> <20100318132014.GA11342@rectangular.com> <9ac0c6aa1003180833l19975560s2a589a9733e7400a@mail.gmail.com> <8f0ad1f31003180926w2b0a80b3i25fdea9a33a68e9c@mail.gmail.com> Date: Thu, 18 Mar 2010 12:12:50 -0500 Message-ID: <9ac0c6aa1003181012j374b5a93oba12dd276905249d@mail.gmail.com> Subject: Re: rough outline of where Solr's going From: Michael McCandless To: solr-dev@lucene.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org Ahh, OK. Meaning Solr will have to remove deprecated support, which means Solr's next released version would be a major release? Ie 2.0? Mike On Thu, Mar 18, 2010 at 11:26 AM, Robert Muir wrote: > On Thu, Mar 18, 2010 at 11:33 AM, Michael McCandless > wrote: >> On version numbering... my inclination would be to let Solr and Lucene >> use their own version numbers (don't sync them up). =A0I know it'd >> simplify our lives to have the same version across the board, but >> these numbers are really for our users, telling them when big changes >> were made, back compat broken, etc. =A0I think that trumps dev >> convenience. > > Be sure to consider the deprecations removal, its not possible for > Solr to move to Lucene's trunk without this. > > Here are two examples of necessary deprecation removals in the branch > so that Solr can use Lucene's trunk: > https://issues.apache.org/jira/browse/SOLR-1820 > http://www.lucidimagination.com/search/document/f07da8e4d69f5bfe/removal_= of_deprecated_htmlstrip_tokenizer_factories > > It seems to be the consensus that people want a major version change > number when this is done. > > So this is an example where the version numbers of Solr really do > relate to Lucene, if we want them to share the same trunk. > > > -- > Robert Muir > rcmuir@gmail.com >