Mailing-List: contact general-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: general@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of bhuvaneswaran@gmail.com
 designates 209.85.160.41 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:reply-to:in-reply-to:references:date:message-id
         :subject:from:to:content-type:content-transfer-encoding;
        b=wHBijugE+emP7JXj0gzkxeX/4ppVetlUHPY6gxuSDlwwoSCdO49dhAMPy7uKwJLuc0
         TmcViL5I0yraDWXBnWh9dhH6pMjX/PT7HA46N1UC6cviA6r9TJJ2m6nG/uTDcipn515L
         a06Qnz9nId8EkoazFR1K9OYXDZDk64AVIbY/s=
MIME-Version: 1.0
Reply-To: bhuvaneswaran@gmail.com
In-Reply-To: <2CFCBE46-7916-47B1-BB80-05309AA2221F@mail.utexas.edu>
References: <4dc6c9040912020948j5ccbb31wf61da8ee3c5e9124@mail.gmail.com>
	 <4B16AF4F.8090601@apache.org>
	 <4239a4320912021809u177f080ai208e2d18846168ad@mail.gmail.com>
	 <4B17F5FB.3010003@apache.org>
	 <4239a4320912031414i528d4e13n74447bb26f522654@mail.gmail.com>
	 <2CFCBE46-7916-47B1-BB80-05309AA2221F@mail.utexas.edu>
Date: Fri, 4 Dec 2009 08:48:51 +0530
Message-ID: <4dc6c9040912031918x6eb7702x119f3a1399cff53f@mail.gmail.com>
Subject: Re: Publishing api docs for Subversion
From: Bhuvaneswaran A <bhuvaneswaran@gmail.com>
To: general@incubator.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Fri, Dec 4, 2009 at 4:23 AM, Hyrum K. Wright
<hyrum_wright@mail.utexas.edu> wrote:
>
> On Dec 3, 2009, at 2:14 PM, Paul Querna wrote:
>
>> On Thu, Dec 3, 2009 at 9:31 AM, Doug Cutting <cutting@apache.org> wrote:
>>> Paul Querna wrote:
>>>>
>>>> httpd and apr have published doxygen of their trunks periodically,
>>>> they aren't based on any release.
>>>
>>> Were these published these on the official public website or in the dev=
/
>>> section?
>>>
>>> I was under the impression that released documentation should be treate=
d
>>> similarly to released code. =A0The convention I've used is that stuff t=
hat's
>>> in trunk, stuff that's intended to be included in releases, is only
>>> published after release. =A0Other pages on the website that are not inc=
luded
>>> in releases, e.g., the project's home page, are clearly published witho=
ut a
>>> release vote.
>>
>> <http://httpd.apache.org/docs/trunk/>
>>
>> Which is linked from the sidebar everywhere, and on the docs page:
>> <http://httpd.apache.org/docs/>
>
> Back the original question: What's the best/typical way of generating and=
 providing these documents? =A0Subversion is using svnwcsub to publish subv=
esion.apache.org, but I don't think it's reasonable to check in a copy of t=
he API documentation.

To add to it and if i was not clear in my original email, when I say
"update docs on nightly basis", I mean updating the files every night.
It does not mean generating new set of doc files every night. Overall
we'll maintain just one copy that is updated every night. I wish there
should be a place other that site/ area in repository, if
people.apache.org is not apt.

--=20
Regards,
Bhuvaneswaran A
www.livecipher.com
GPG: 0x7A13E5B0

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org