Received: by taz.hyperreal.com (8.7.6/V2.0) id OAA05859; Sun, 3 Nov 1996 14:11:00 -0800 (PST) Received: from eat.organic.com by taz.hyperreal.com (8.7.6/V2.0) with ESMTP id OAA05852; Sun, 3 Nov 1996 14:10:57 -0800 (PST) Received: from localhost (brian@localhost) by eat.organic.com (8.7.5/8.7.3) with SMTP id OAA02679 for ; Sun, 3 Nov 1996 14:11:11 -0800 (PST) Date: Sun, 3 Nov 1996 14:11:11 -0800 (PST) From: Brian Behlendorf To: new-httpd@hyperreal.com Subject: Re: Documentation In-Reply-To: <9610311949.aa25235@gonzo.ben.algroup.co.uk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-new-httpd@apache.org Precedence: bulk Reply-To: new-httpd@hyperreal.com On Thu, 31 Oct 1996, Ben Laurie wrote: > > I'm concerned about exactly how this works - if I commit a change, > > does it update the documents in the www.apache.org document root as > > well? If not, how do those docs get updated, since that is, after all, > > the point of the exercise (to maintain the docs on the web page). > > I would have thought that the correct thing to do is to release the docs > periodically. Alternatively we can have a snapshot system, much like the > current Apache snapshot, only not tarred up! > > Or even both. > > Of course, this is one good argument for having a completely separate > repository for the docs, since they would doubtless be released asynchronously > with the code. My thoughts: 1) There's not a requirement, in my mind, for holding changes in the doc trees for a long amount of time; meaning, I would be comfortable if the docs were pointed at a reflection of the CVS tree. 2) Updates every 6-hours are alright, but ideally there's a "button" one could push when they've committed a change which pushes a new reflection out. 3) We should avoid having any CVS gunk in the live site. Brian --=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-- brian@organic.com www.apache.org hyperreal.com http://www.organic.com/JOBS