Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
MIME-Version: 1.0
In-Reply-To: <CAOqetn8DoyGT33Jtzr80TxmaTBLpQ0rmEk=a_eo6VVKMX0YVLw@mail.gmail.com>
References: <CAOqetn89onw7wghmoV2YES6BMsN6BXrM-R4VyEXLOqxEvWGWag@mail.gmail.com>
 <1384148928.13193786.1478894252420.JavaMail.zimbra@redhat.com> <CAOqetn8DoyGT33Jtzr80TxmaTBLpQ0rmEk=a_eo6VVKMX0YVLw@mail.gmail.com>
From: Clebert Suconic <clebert.suconic@gmail.com>
Date: Mon, 14 Nov 2016 10:28:54 -0500
Message-ID: <CAKF+bsp8rPsG3oRxaAOw_NMpyFmQPzpi=zSaynwkq8JVEC7n8Q@mail.gmail.com>
Subject: Re: How to rebuild the docs for Artemis?
To: "dev@activemq.apache.org" <dev@activemq.apache.org>
Content-Type: text/plain; charset=UTF-8
archived-at: Mon, 14 Nov 2016 15:29:05 -0000

> I'm against the idea of storing the docs outside the source repository.  It
> just makes sense for them to live together.  When you're looking at a
> release bundle, the docs within it should match the release you pulled down.
>
> I don't have an issue with us hosting multiple releases worth of docs, even
> though at apache we only ever consider the latest release as valid.  I
> think it would be beneficial for us to have docs setup for the current
> snapshot as well.  This way we can see if users have feedback on the
> current goings on.  That's where I'm talking about the continuous aspect of
> this.  They could even go into a SNAPSHOT folder.
>

That would encourage snapshot usage IMO.

As of now I will just update 1.5.0 HTML with the change you made.