<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p>Just FYI there's documentation framework decision going on on
Linux Kernel these days:<br>
</p>
<p><a class="moz-txt-link-freetext" href="http://lwn.net/Articles/692704/">http://lwn.net/Articles/692704/</a></p>
<p>There are pros and cons being evaluated of different doc.
generation frameworks.<br>
</p>
<p>Rio<br>
</p>
<br>
<div class="moz-cite-prefix">On 07/25/2016 08:46 PM, James Perkins
wrote:<br>
</div>
<blockquote
cite="mid:CADGwLpiWu=wtQ6n-Y4yozqWaJcG=VTmk=C_LF95LbXaXc1mZiQ@mail.gmail.com"
type="cite">
<div dir="ltr"><br>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Mon, Jul 25, 2016 at 10:57 AM,
Emmanuel Hugonnet <span dir="ltr"><<a
moz-do-not-send="true" href="mailto:ehugonne@redhat.com"
target="_blank">ehugonne@redhat.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
Should we have a maintenance branch for the current stable
version documentation (maybe on gitbook) and a living
documentation (using github<br>
rendering) or just the living doc ?<br>
<span class=""><br>
</span>
<div class="HOEnZb">
<div class="h5"><br>
</div>
</div>
</blockquote>
<div><br>
</div>
<div>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.</div>
<div><br>
</div>
<div>Regardless of the framework it could be a bit tricky
for micro-releases if master has already changed when
making a snapshot.</div>
<div> </div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="HOEnZb">
<div class="h5">
</div>
</div>
<br>
_______________________________________________<br>
wildfly-dev mailing list<br>
<a moz-do-not-send="true"
href="mailto:wildfly-dev@lists.jboss.org">wildfly-dev@lists.jboss.org</a><br>
<a moz-do-not-send="true"
href="https://lists.jboss.org/mailman/listinfo/wildfly-dev"
rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/wildfly-dev</a><br>
</blockquote>
</div>
<br>
<br clear="all">
<div><br>
</div>
-- <br>
<div class="gmail_signature" data-smartmail="gmail_signature">
<div dir="ltr">
<div>
<div dir="ltr">
<div>James R. Perkins</div>
<div>JBoss by Red Hat</div>
</div>
</div>
</div>
</div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
wildfly-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:wildfly-dev@lists.jboss.org">wildfly-dev@lists.jboss.org</a>
<a class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/wildfly-dev">https://lists.jboss.org/mailman/listinfo/wildfly-dev</a></pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Richard Opalka
Principal Software Engineer
Red Hat JBoss Middleware
Mobile: +420 731 186 942
E-mail: <a class="moz-txt-link-abbreviated" href="mailto:ropalka@redhat.com">ropalka@redhat.com</a>
</pre>
</body>
</html>