incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Branko ─îibej <>
Subject Re: Publishing api docs for Subversion
Date Sat, 05 Dec 2009 12:58:24 GMT
sebb wrote:
> On 03/12/2009, Paul Querna <> wrote:
>> On Wed, Dec 2, 2009 at 10:17 AM, Doug Cutting <> wrote:
>>  > Bhuvaneswaran A wrote:
>>  >>
>>  >> We tend to update the api docs generated using doxygen and java doc on
>>  >> a nightly basis.
>>  >
>>  > Unreleased artifacts should be linked only from the developer portion of the
>>  > site and should not be hosted on the official project site.  You might,
>>  > e.g., just link to them on the Hudson server rather than copy them to
>>  >  Documentation should only be published to the official
>>  > website after it's been included in an Apache release. This is for legal
>>  > reasons: we work hard to ensure that releases have licensing in order, but
>>  > do not in general guarantee that licensing is correct at all times in source
>>  > code repositories.
>> I'm sorry what?
>>  httpd and apr have published doxygen of their trunks periodically,
>>  they aren't based on any release.
> And large parts of the ASF website (which can be considered as
> documentation) are not subject to formal "release" votes.
> Doug's comments seem OK if they refer to code releases, but surely
> documentation is not subject to release votes?

Actually, we're talking about API documentation which in Subversion's
case is generated from the sources, so yes, it is subject to release
votes. But only for actual releases.

Restricting the publishing of generated API documentation would imply
that we should restrict access to ViewVC, too, because anyone can browse
that exact same documentation through that, albeit formatted a bit

-- Brane

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message