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 ekoneil@gmail.com designates
 66.249.92.172 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=lK09X1quFbB59YYDhDmtk6CfCp6nxCh5PoDjP9DP1nvxjnMZ2Hxam9d8f6ohGHqTKqp9Y4D8AfFx6lZ8T9FqPgIJMvZ2iaNYRFrExWvufIMDJujWK1CDT+B+qKfL2LfybgUtKrclp4c8/uTnLqDtebBEXqZIuFY0TNGijUfO8sE=
Message-ID: <e9ac83540701151649t5c388f8cpc3c70f6a565e8d14@mail.gmail.com>
Date: Mon, 15 Jan 2007 17:49:03 -0700
From: "Eddie O'Neil" <ekoneil@gmail.com>
To: "Beehive Developers" <dev@beehive.apache.org>
Subject: Re: Need to fix the 1.0.2 installation document
In-Reply-To: <ba6911de0701151647k23e22a9fo5e730d4e9d5a75c9@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <ba6911de0701151008n3860b2e9j91135366e16ad54c@mail.gmail.com>
	 <e9ac83540701151018q4e7f6bc8y981b4e388a5dedbe@mail.gmail.com>
	 <ba6911de0701151446mee61b33tb3a3822b008078cb@mail.gmail.com>
	 <e9ac83540701151542r4a745f4cw755a5efe2a4de1ce@mail.gmail.com>
	 <ba6911de0701151613qaecbc97t5e864c67adab037@mail.gmail.com>
	 <e9ac83540701151638pbafbdaem74c8ac561f6d3a7@mail.gmail.com>
	 <ba6911de0701151647k23e22a9fo5e730d4e9d5a75c9@mail.gmail.com>

  Great!  Thanks for taking care of it.  I'll put together a HOWTO on
the wiki that covers some of these kinds of tasks.

Eddie


On 1/15/07, Carlin Rogers <carlin.rogers@gmail.com> wrote:
> Excellent. Thanks for all the information. I've copied the new files
> into /www/beehive.apache.org/docs/1.0.2/. The permissions seem to be
> fine.
>
> Thanks,
> Carlin
>
> On 1/15/07, Eddie O'Neil <ekoneil@gmail.com> wrote:
> > Carlin--
> >
> >   Good question -- it's best to use people.apache.org, but any machine
> > should give you access to the same underlying file system.  It's
> > probably easiest to scp the files to:
> >
> >   /www/beehive.apache.org/docs/1.0.2/
> >
> > which is a directory in the ASF file system.  Then you can ssh to
> > people.apache.org machine to ensure that the permissions are set
> > correctly.  Once this is done, it will take an hour or so before
> > changed content is mirrored to the live web servers, so don't be
> > concerned if your changes aren't visible for a while.  :)
> >
> >   The ASF Infrastructure team owns administering these machines; more
> > information on ASF infrastructure is here:
> >
> >   http://www.apache.org/dev/
> >
> > or in the infrastructure@ mailing list.
> >
> >   Hope that helps.
> >
> > Eddie
> >
> > On 1/15/07, Carlin Rogers <carlin.rogers@gmail.com> wrote:
> > > Eddie,
> > >
> > > Does it matter which apache.org machine I use to update the site
> > > files? From an old email I have, there was a comment about
> > > minotaur.apache.org. I'm not familiar with the process for replicating
> > > the web site and just wanted to verify the Apache process for this. Is
> > > there an Apache page with this info?
> > >
> > > Many thanks,
> > > Carlin
> > >
> > > On 1/15/07, Eddie O'Neil <ekoneil@gmail.com> wrote:
> > > > Carlin--
> > > >
> > > >   I've updated the permissions on the entire /www/beehive.apache.org/
> > > > directory, so this should be writable to you and anyone else in the
> > > > "beehive" group.
> > > >
> > > >   As far as signing the documentation kits, I don't think that this is
> > > > necessary, especially if the website is updated.  Since Apache
> > > > releases are created by a vote on an SVN change number, any release of
> > > > new bits would require a re-vote on a new SVN changelist.  If this was
> > > > a fix for an egregious bug, I'd agree that we should re-release, but
> > > > in this case it seems fine to live with this issue.
> > > >
> > > >   My $0.02.
> > > >
> > > > Eddie
> > > >
> > > >
> > > >
> > > > On 1/15/07, Carlin Rogers <carlin.rogers@gmail.com> wrote:
> > > > > Eddie,
> > > > >
> > > > > I checked in the fix for the link issue. However, I don't have a key
> > > > > to sign the documentation kits. Can you post these? Thanks.
> > > > >
> > > > > I also tried to copy the new single changed page and associated PDF
> > > > > file into the /www/beehive.apache.org/docs/1.0.2 directory but was
> > > > > unable to because of permissions. It looks like the file is only
> > > > > writable by you. If you change the permissions, I can copy the new
> > > > > files into place.
> > > > >
> > > > > Thanks,
> > > > > 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
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>