Mailing-List: contact dev-help@beehive.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Beehive Developers" <dev@beehive.apache.org>
Received-SPF: pass (herse.apache.org: domain of carlin.rogers@gmail.com
 designates 66.249.82.229 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=m/r0U8nOZHC1BswM4QuB1x7L1+NyhoeRzGJq1WNDWd6x6yI624iZ3f/R5pC9eNIJT32+iEi8XGm0pqewSvoR7E6ovA+3HQOJiVzloSylgG4WoVlKnTW49WruyCfDNaGEW8LK40TwVep611hTLcy7lahvqgcLi/sZiaYPprnQAKo=
Message-ID: <ba6911de0701151032g2203bf46uff1117984d222367@mail.gmail.com>
Date: Mon, 15 Jan 2007 11:32:31 -0700
From: "Carlin Rogers" <carlin.rogers@gmail.com>
To: "Beehive Developers" <dev@beehive.apache.org>
Subject: Re: Need to fix the 1.0.2 installation document
In-Reply-To: <e9ac83540701151018q4e7f6bc8y981b4e388a5dedbe@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <ba6911de0701151008n3860b2e9j91135366e16ad54c@mail.gmail.com>
	 <e9ac83540701151018q4e7f6bc8y981b4e388a5dedbe@mail.gmail.com>

Thanks Eddie. I'll give it a go and let you know if I have any questions.

Carlin

On 1/15/07, Eddie O'Neil <ekoneil@gmail.com> wrote:
> Carlin--
>
>   It's good that someone caught that.  :)
>
> This would just follow the usual way of updating a release
> documentation kit, namely:
> #1) Commit an update to branches/v1.0.2/... that fixes the problem
> #2) Rebuild the documentation kit (see Ant targets in branches/v1.0.2/build.xml)
> #3) Update the live website hosted in
> /www/beehive.apache.org/docs/1.0.2 with the new documentation kit,
> single changed page, etc.
>
> I'll make sure that this is captured in a wiki page somewhere.  Let me
> know if you have questions.
>
> Thanks!
> Eddie
>
>
> On 1/15/07, Carlin Rogers <carlin.rogers@gmail.com> wrote:
> > Eddie,
> >
> > I was wondering what the process was to update a release build
> > document (not the site documents) out on the beehive web site.
> >
> > Greg Mally caught an issue with the 1.0.2 installation document,
> > http://beehive.apache.org/docs/1.0.2/installation.html
> >
> > The document has the correct text in the link for the download,
> > release-1.0.2.cgi. However, the actual link that was generated from
> > the installation.xml for href="site:beehive-release/current" points to
> > release-1.0.cgi.
> >
> > The installation.html document in the distribution has the same issue
> > but it's probably best to at least fix the document out on the Web
> > site.
> >
> > I can take care of this if you'd like but just wanted to know the
> > process for doing something like this.
> >
> > Thanks,
> > Carlin
> >
>