Mailing-List: contact dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@lucene.apache.org
Received-SPF: pass (athena.apache.org: domain of yseeley@gmail.com designates
 209.85.161.48 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:sender:reply-to:in-reply-to:references:date
         :x-google-sender-auth:message-id:subject:from:to:cc:content-type
         :content-transfer-encoding;
        b=X2boEysARmoRyrSKyqynjTrKclNUzTzY6n0RvW2IQFfObc97rSgmhmIpLAMPpkeAob
         1XrQQf+uEZYIEuEaq7Cc8DIC+65Kkpc4amS6WkogssERsx8PL/9iqSvKllZTJpYNPZSi
         tDJ7MeO577fV1NTmCGZe5AwlAloh7w6H9pBR4=
MIME-Version: 1.0
Sender: yseeley@gmail.com
Reply-To: yonik@lucidimagination.com
In-Reply-To: <alpine.DEB.2.00.1103171743350.24286@bester>
References: <AANLkTimntcRktKMaYaBY10S9hPLS8yy1otXpDP2KVNyH@mail.gmail.com>
	<alpine.DEB.2.00.1103171249090.24286@bester>
	<alpine.DEB.2.00.1103171743350.24286@bester>
Date: Thu, 17 Mar 2011 21:04:59 -0400
Message-ID: <AANLkTineUfbawW9d+2Qk=mX9U7Wq+=U4-ZawCgQpEU_v@mail.gmail.com>
Subject: Re: Lucene Solr 3.1 RC1
From: Yonik Seeley <yonik@lucidimagination.com>
To: Chris Hostetter <hossman_lucene@fucit.org>
Cc: Lucene Dev <dev@lucene.apache.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

IMO, I think our source release should be what you get when you do a
checkout from SVN.
Building from source is more expert level, and one needs (minimally) ant se=
t up.

If I do another RC, I'm half-way convinced I should just do an "svn
export" and tar it up.  No .zip... anyone handling a source release
should know what to do with a .tgz   Attempting to automate it by
yanking just the right stuff out of a superset is just so error prone.

As far as docs - I think most people look online first?  They would
certainly look online if they didn't see anything local.

-Yonik

On Thu, Mar 17, 2011 at 8:47 PM, Chris Hostetter
<hossman_lucene@fucit.org> wrote:
>
> : * nothing in README or "ant -p" about how to build the non-javadocs (ie=
:
> : tutorial)
>
> we could add a one liner about this to the README.txt...
>
> =A0 =A0 =A0 =A0Run the forrest command in the src/site directory to build=
 the tutorial
>
> ...but the more i think about it the more i'm convinced that we should
> just include the pre-build "site" directory in the source packages
>
> this is consistent with what we do for the lucene source packages -- we
> actually have the html/pdf versions of hte lucene forrest docs in the sol=
r
> source packages, but not the solr forrest docs.
>
>
> -Hoss
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org