[wildfly-dev] One Doc to Rule Them All

[James Perkins]

On Mon, Jul 25, 2016 at 10:57 AM, Emmanuel Hugonnet <ehugonne at redhat.com>
wrote:

> Hi,
> Should we have a maintenance branch for the current stable version
> documentation (maybe on gitbook) and a living documentation (using github
> rendering) or just the living doc ?
>
>
>
I think it kind of depends on the framework we choose. If we stick with
Confluence I think we could just have a WFLY document id and then once we
release we make a copy of that version. The downside is if you do find a
mistake you might have to change it in a few different spots.

Regardless of the framework it could be a bit tricky for micro-releases if
master has already changed when making a snapshot.


>
> _______________________________________________
> wildfly-dev mailing list
> wildfly-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>



-- 
James R. Perkins
JBoss by Red Hat
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/wildfly-dev/attachments/20160725/a30aab8c/attachment.html