Return-Path: Delivered-To: apmail-hadoop-avro-user-archive@minotaur.apache.org Received: (qmail 77069 invoked from network); 20 Feb 2010 00:22:40 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 20 Feb 2010 00:22:40 -0000 Received: (qmail 24649 invoked by uid 500); 20 Feb 2010 00:22:40 -0000 Delivered-To: apmail-hadoop-avro-user-archive@hadoop.apache.org Received: (qmail 24582 invoked by uid 500); 20 Feb 2010 00:22:39 -0000 Mailing-List: contact avro-user-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: avro-user@hadoop.apache.org Delivered-To: mailing list avro-user@hadoop.apache.org Received: (qmail 24573 invoked by uid 99); 20 Feb 2010 00:22:39 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 20 Feb 2010 00:22:39 +0000 X-ASF-Spam-Status: No, hits=3.4 required=10.0 tests=HTML_MESSAGE,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [209.85.221.184] (HELO mail-qy0-f184.google.com) (209.85.221.184) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 20 Feb 2010 00:22:33 +0000 Received: by qyk14 with SMTP id 14so415985qyk.9 for ; Fri, 19 Feb 2010 16:22:12 -0800 (PST) MIME-Version: 1.0 Received: by 10.229.219.143 with SMTP id hu15mr703327qcb.12.1266624834646; Fri, 19 Feb 2010 16:13:54 -0800 (PST) In-Reply-To: <4B7F28A8.9010506@apache.org> References: <4B7F28A8.9010506@apache.org> Date: Fri, 19 Feb 2010 16:13:54 -0800 Message-ID: Subject: Re: Host the spec as it looks in trunk somewhere? From: Jeff Hammerbacher To: avro-user@hadoop.apache.org Content-Type: multipart/alternative; boundary=0016361640795532bb047ffd13a2 --0016361640795532bb047ffd13a2 Content-Type: text/plain; charset=ISO-8859-1 That's fine. I just want something to point to so that I can say, "here's the spec for the previous release; we've made some changes, nothing finalized, that you can see here: xxx". On Fri, Feb 19, 2010 at 4:11 PM, Doug Cutting wrote: > As soon as we make the 1.3 release, we'll post the new version of the spec. > If we had Hudson nightly builds, then they could include the trunk version > of the spec. We shouldn't publish an unreleased spec on the official > website. > > Doug > > > Jeff Hammerbacher wrote: > >> Hey, >> >> We've evolved the spec quite a bit since the 1.2 release, and it would be >> nice to have a public web page with the state of the spec as it currently >> stands. Any opinions on hosting the spec for trunk somewhere? >> >> Thanks, >> Jeff >> > --0016361640795532bb047ffd13a2 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable That's fine. I just want something to point to so that I can say, "= ;here's the spec for the previous release; we've made some changes,= nothing finalized, that you can see here: xxx".

On Fri, Feb 19, 2010 at 4:11 PM, Doug Cutting <cutting@apache.org> wrote:
=
As soon as we make the 1.3 release, we'll post the new version of the s= pec. =A0If we had Hudson nightly builds, then they could include the trunk = version of the spec. =A0We shouldn't publish an unreleased spec on the = official website.

Doug


Jeff Hammerbacher wrote:
Hey,

We've evolved the spec quite a bit since the 1.2 release, and it would = be nice to have a public web page with the state of the spec as it currentl= y stands. Any opinions on hosting the spec for trunk somewhere?

Thanks,
Jeff

--0016361640795532bb047ffd13a2--