Mailing-List: contact dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@lucene.apache.org
Received-SPF: pass (nike.apache.org: domain of rcmuir@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:in-reply-to:references:from:date:message-id:subject:to
         :content-type;
        b=Ui5cA9p3mzfCC0A8pcISI6mHmVLKhfJsqVo3Vgq+OV+qKziecGx+ifedwWQf1qFNEz
         UUjC4T0MwZF087aMDEDcUuYfDrvhdSPMZfMDBHXzyv0jnkVdZEdiXRzhntdgEi+1ztxT
         sjrOEDibv8nQhTA2ZdGTRYTAYlpEgHhwERdn4=
MIME-Version: 1.0
In-Reply-To: <739C0A1E-4E5C-459D-9776-144E702D66FE@apache.org>
References: <AANLkTinx18uNyGRq5pF90OkU+H2jFT2WC1DYagiGWrqQ@mail.gmail.com>
 <C8BA6C96.1ECE3%Chris.A.Mattmann@jpl.nasa.gov>
 <AANLkTinQWhSnxWbzjBMem78qhVJpXz9K7Frg1yh5mxVe@mail.gmail.com>
 <AANLkTi=E2vEGVm5dF1EbmFiitTJd=gWOW+Basp3yRm8U@mail.gmail.com>
 <7A5D88B2-EC13-43E3-A175-7A8C550FC9F8@apache.org>
 <4C975ADB.2080607@gmail.com>
 <AANLkTimqUWMm5be7SJn0zwnALHUEeGT-tje_wEU+=Wmc@mail.gmail.com>
 <4E5D3286-141F-4422-8D0A-CB48623DD2CD@apache.org>
 <AANLkTinFJFwEG8wyZKc49x_x4XP7VWDmgOe5TK_T1XM7@mail.gmail.com>
 <AANLkTino9y1_u7fmpVS9_4cQ+1g31TjEyEKjBTfyWqFx@mail.gmail.com>
 <AANLkTinakvAMhGShLzcjGB-9Tiv7d=Z6w3wtK97QtR6m@mail.gmail.com>
 <AANLkTimrcUub8MACK0PFguSfS8x2VX1w9Sj8D4nupoUH@mail.gmail.com>
 <004501cb58e4$8886bb30$99943190$@thetaphi.de>
 <AANLkTintc+A=ncTOUWGZO43Y-hgwu47dA+bTB5KYux0m@mail.gmail.com>
 <FC1FD941-4709-4015-91B6-BD02509201EE@apache.org>
 <AANLkTinRFjrcoyYuWUhSY0T0U1Xp9x9+GO8QKOin3Hq8@mail.gmail.com>
 <69F211AC-9651-4C99-A653-79FC2EDD1373@apache.org>
 <80C13519-3CB9-407F-BBC2-4359DB792B2F@apache.org>
 <AANLkTincbBsCqqZ-1STcH0gng-pVo4i7ECoczDiGBk73@mail.gmail.com>
 <739C0A1E-4E5C-459D-9776-144E702D66FE@apache.org>
From: Robert Muir <rcmuir@gmail.com>
Date: Mon, 20 Sep 2010 15:49:46 -0400
Message-ID: <AANLkTinrMZUy8UJf=54dVhbTPceyBLmv+NV2Xc=DgUmX@mail.gmail.com>
Subject: Re: discussion about release frequency.
To: dev@lucene.apache.org
Content-Type: multipart/alternative; boundary=001636c59a341608f40490b63893

--001636c59a341608f40490b63893
Content-Type: text/plain; charset=UTF-8

On Mon, Sep 20, 2010 at 3:46 PM, Grant Ingersoll <gsingers@apache.org>wrote:

>
> Why don't we just leave this as this:
>
> Those of us who want Maven supported as part of the release need to get our
> stuff together by the next release or else it will be dropped.  That means
> making sure the artifacts are correct and easily testable/reproducible.  If
> we can't do that, then I agree, it should be a downstream effort, at least
> until we all realize how many people actually use it and then we revisit it
> at the next release.
>
>
But I'm not sure this is the best solution? If we can push this downstream,
so that the release manager has less to worry about (even with testable
artifacts etc, the publication etc), why wouldn't we do that instead?

-- 
Robert Muir
rcmuir@gmail.com

--001636c59a341608f40490b63893
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<br><br><div class=3D"gmail_quote">On Mon, Sep 20, 2010 at 3:46 PM, Grant I=
ngersoll <span dir=3D"ltr">&lt;<a href=3D"mailto:gsingers@apache.org">gsing=
ers@apache.org</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" s=
tyle=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">

<div style=3D"word-wrap:break-word"><div><div></div><div class=3D"h5"><div>=
<br></div></div></div><div>Why don&#39;t we just leave this as this:</div><=
div><br></div><div>Those of us who want Maven supported as part of the rele=
ase need to get our stuff together by the next release or else it will be d=
ropped. =C2=A0That means making sure the artifacts are correct and easily t=
estable/reproducible. =C2=A0If we can&#39;t do that, then I agree, it shoul=
d be a downstream effort, at least until we all realize how many people act=
ually use it and then we revisit it at the next release.</div>

<div><font class=3D"Apple-style-span" color=3D"#888888"><font class=3D"Appl=
e-style-span" color=3D"#000000"><br></font></font></div></div></blockquote>=
</div><div><br></div>But I&#39;m not sure this is the best solution? If we =
can push this downstream, so that the release manager has less to worry abo=
ut (even with testable artifacts etc, the publication etc), why wouldn&#39;=
t we do that instead?<br clear=3D"all">

<br>-- <br>Robert Muir<br><a href=3D"mailto:rcmuir@gmail.com">rcmuir@gmail.=
com</a><br>

--001636c59a341608f40490b63893--