Just FYI there's documentation framework decision going on on Linux Kernel these days:

http://lwn.net/Articles/692704/

There are pros and cons being evaluated of different doc. generation frameworks.

Rio

On Mon, Jul 25, 2016 at 10:57 AM, Emmanuel Hugonnet <ehugonne@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@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/wildfly-dev

--

James R. Perkins

JBoss by Red Hat

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

-- 
Richard Opalka
Principal Software Engineer
Red Hat JBoss Middleware
Mobile: +420 731 186 942
E-mail: ropalka@redhat.com